Wireless Device and Wireless Network Processes in Inactive State

ABSTRACT

A wireless device receives an RRC release message comprising first configuration parameter(s), second configuration parameter(s) and third configuration parameter(s). The first configuration parameter(s) may indicate transitioning from an RRC connected state to an RRC inactive state. The second configuration parameter(s) may be of a configured grant configuration associated with small data transmission in the RRC inactive state. The third configuration parameter(s) may be of a time alignment timer associated with small data transmission in the RRC inactive state. The wireless device may start the time alignment timer in response to receiving the RRC release message and based on the third configuration parameter(s). The wireless device may transmit a transport block, while in the RRC inactive state, based on radio resources of a first configured grant associated with the configured grant configuration and based on the time alignment timer running.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/976,271, filed Feb. 13, 2020, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A and FIG. 1B show examples of mobile communications systems inaccordance with several of various embodiments of the presentdisclosure.

FIG. 2A and FIG. 2B show examples of user plane and control planeprotocol layers in accordance with several of various embodiments of thepresent disclosure.

FIG. 3 shows example functions and services offered by protocol layersin a user plane protocol stack in accordance with several of variousembodiments of the present disclosure.

FIG. 4 shows example flow of packets through the protocol layers inaccordance with several of various embodiments of the presentdisclosure.

FIG. 5A shows example mapping of channels between layers of the protocolstack and different physical signals in downlink in accordance withseveral of various embodiments of the present disclosure.

FIG. 5B shows example mapping of channels between layers of the protocolstack and different physical signals in uplink in accordance withseveral of various embodiments of the present disclosure.

FIG. 6 shows example physical layer processes for signal transmission inaccordance with several of various embodiments of the presentdisclosure.

FIG. 7 shows examples of RRC states and RRC state transitions inaccordance with several of various embodiments of the presentdisclosure.

FIG. 8 shows an example time domain transmission structure in NR bygrouping OFDM symbols into slots, subframes and frames in accordancewith several of various embodiments of the present disclosure.

FIG. 9 shows an example of time-frequency resource grid in accordancewith several of various embodiments of the present disclosure.

FIG. 10 shows example adaptation and switching of bandwidth parts inaccordance with several of various embodiments of the presentdisclosure.

FIG. 11A shows example arrangements of carriers in carrier aggregationin accordance with several of various embodiments of the presentdisclosure.

FIG. 11B shows examples of uplink control channel groups in accordancewith several of various embodiments of the present disclosure.

FIG. 12A, FIG. 12B and FIG. 12C show example random access processes inaccordance with several of various embodiments of the presentdisclosure.

FIG. 13A shows example time and frequency structure of SSBs and theirassociations with beams in accordance with several of variousembodiments of the present disclosure.

FIG. 13B shows example time and frequency structure of CSI-RSs and theirassociation with beams in accordance with several of various embodimentsof the present disclosure.

FIG. 14A, FIG. 14B and FIG. 14C show example beam management processesin accordance with several of various embodiments of the presentdisclosure.

FIG. 15 shows example components of a wireless device and a base stationthat are in communication via an air interface in accordance withseveral of various embodiments of the present disclosure.

FIG. 16 shows an example UE triggered transition from RRC_INACTIVE toRRC_CONNECTED in accordance with several of various embodiments of thepresent disclosure.

FIG. 17 shows an example UE triggered transition from RRC_INACTIVE toRRC_CONNECTED in accordance with several of various embodiments of thepresent disclosure.

FIG. 18 shows an example RRC resume request with network rejection inaccordance with several of various embodiments of the presentdisclosure.

FIG. 19 shows an example network triggered transition from RRC_INACTIVEto RRC_CONNECTED in accordance with several of various embodiments ofthe present disclosure.

FIG. 20 shows an example RAN notification area (RNA) update procedure inaccordance with several of various embodiments of the presentdisclosure.

FIG. 21 shows an example periodic RNA update procedure in accordancewith several of various embodiments of the present disclosure.

FIG. 22 shows an example RNA update procedure in accordance with severalof various embodiments of the present disclosure.

FIG. 23 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 24 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 25 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 26 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 27 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 28 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 29 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 30 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 31 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 32 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 33 shows example MAC CE formats in accordance with several ofvarious embodiments of the present disclosure.

FIG. 34 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 35 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 36 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 37 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 38 shows multiplexing processes in accordance with several ofvarious embodiments of the present disclosure.

FIG. 39A and FIG. 39B show example logical channel configurationparameters in accordance with several of various embodiments of thepresent disclosure.

FIG. 40 shows an example multiplexing process in accordance with severalof various embodiments of the present disclosure.

FIG. 41 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 42 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 43 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 44 shows example multiplexing processes in accordance with severalof various embodiments of the present disclosure.

FIG. 45 shows example processes in accordance with several of variousembodiments of the present disclosure.

FIG. 46 shows example processes in accordance with several of variousembodiments of the present disclosure.

FIG. 47 shows an example data transmission process in inactive state inaccordance with several of various embodiments of the presentdisclosure.

FIG. 48 shows an example data transmission process in inactive state inaccordance with several of various embodiments of the presentdisclosure.

FIG. 49 shows an example data transmission process in inactive state inaccordance with several of various embodiments of the presentdisclosure.

FIG. 50 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 51 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 52 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 53 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 54 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 55 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 56 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 57 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 58 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 59 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 60 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 61 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 62 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 63 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

DETAILED DESCRIPTION

The exemplary embodiments of the disclosed technology enable operationof a wireless device and/or one or more base stations in inactive state.The exemplary disclosed embodiments may be implemented in the technicalfield of wireless communication systems. More particularly, theembodiment of the disclosed technology may enable wireless device andwireless network processes for data transmission in inactive state.

The devices and/or nodes of the mobile communications system disclosedherein may be implemented based on various technologies and/or variousreleases/versions/amendments of a technology. The various technologiesinclude various releases of long-term evolution (LTE) technologies,various releases of 5G new radio (NR) technologies, various wirelesslocal area networks technologies and/or a combination thereof and/oralike. For example, a base station may support a given technology andmay communicate with wireless devices with different characteristics.The wireless devices may have different categories that define theircapabilities in terms of supporting various features. The wirelessdevice with the same category may have different capabilities. Thewireless devices may support various technologies such as variousreleases of LTE technologies, various releases of 5G NR technologiesand/or a combination thereof and/or alike. At least some of the wirelessdevices in the mobile communications system of the present disclosuremay be stationary or almost stationary. In this disclosure, the terms“mobile communications system” and “wireless communications system” maybe used interchangeably.

FIG. 1A shows an example of a mobile communications system 100 inaccordance with several of various embodiments of the presentdisclosure. The mobile communications system 100 may be, for example,run by a mobile network operator (MNO) or a mobile virtual networkoperator (MVNO). The mobile communications system 100 may be a publicland mobile network (PLMN) run by a network operator providing a varietyof service including voice, data, short messaging service (SMS),multimedia messaging service (MMS), emergency calls, etc. The mobilecommunications system 100 includes a core network (CN) 106, a radioaccess network (RAN) 104 and at least one wireless device 102.

The CN 106 connects the RAN 104 to one or more external networks (e.g.,one or more data networks such as the Internet) and is responsible forfunctions such as authentication, charging and end-to-end connectionestablishment. Several radio access technologies (RATs) may be served bythe same CN 106.

The RAN 104 may implement a RAT and may operate between the at least onewireless device 102 and the CN 106. The RAN 104 may handle radio relatedfunctionalities such as scheduling, radio resource control, modulationand coding, multi-antenna transmissions and retransmission protocols.The wireless device and the RAN may share a portion of the radiospectrum by separating transmissions from the wireless device to the RANand the transmissions from the RAN to the wireless device. The directionof the transmissions from the wireless device to the RAN is known as theuplink and the direction of the transmissions from the RAN to thewireless device is known as the downlink. The separation of uplink anddownlink transmissions may be achieved by employing a duplexingtechnique. Example duplexing techniques include frequency divisionduplexing (FDD), time division duplexing (TDD) or a combination of FDDand TDD.

In this disclosure, the term wireless device may refer to a device thatcommunicates with a network entity or another device using wirelesscommunication techniques. The wireless device may be a mobile device ora non-mobile (e.g., fixed) device. Examples of the wireless deviceinclude cellular phone, smart phone, tablet, laptop computer, wearabledevice (e.g., smart watch, smart shoe, fitness trackers, smart clothing,etc.), wireless sensor, wireless meter, extended reality (XR) devicesincluding augmented reality (AR) and virtual reality (VR) devices,Internet of Things (IoT) device, vehicle to vehicle communicationsdevice, road-side units (RSU), automobile, relay node or any combinationthereof. In some examples, the wireless device (e.g., a smart phone,tablet, etc.) may have an interface (e.g., a graphical user interface(GUI)) for configuration by an end user. In some examples, the wirelessdevice (e.g., a wireless sensor device, etc.) may not have an interfacefor configuration by an end user. The wireless device may be referred toas a user equipment (UE), a mobile station (MS), a subscriber unit, ahandset, an access terminal, a user terminal, a wireless transmit andreceive unit (WTRU) and/or other terminology.

The at least one wireless device may communicate with at least one basestation in the RAN 104. In this disclosure, the term base station mayencompass terminologies associated with various RATs. For example, abase station may be referred to as a Node B in a 3G cellular system suchas Universal Mobile Telecommunication Systems (UMTS), an evolved Node B(eNB) in a 4G cellular system such as evolved universal terrestrialradio access (E-UTRA), a next generation eNB (ng-eNB), a Next GenerationNode B (gNB) in NR and/or a 5G system, an access point (AP) in Wi-Fiand/or other wireless local area networks. A base station may bereferred to as a remote radio head (RRH), a baseband unit (BBU) inconnection with one or more RRHs, a repeater or relay for coverageextension and/or any combination thereof. In some examples, all protocollayers of a base station may be implemented in one unit. In someexample, some of the protocol layers (e.g., upper layers) of the basestation may be implemented in a first unit (e.g., a central unit (CU))and some other protocol layer (e.g., lower layers) may be implemented inone or more second units (e.g., distributed units (DUs)).

A base station in the RAN 104 includes one or more antennas tocommunicate with the at least one wireless device. The base station maycommunicate with the at least one wireless device using radio frequency(RF) transmissions and receptions via RF transceivers. The base stationantennas may control one or more cells (or sectors). The size and/orradio coverage area of a cell may depend on the range that transmissionsby a wireless device can be successfully received by the base stationwhen the wireless device transmits using the RF frequency of the cell.The base station may be associated with cells of various sizes. At agiven location, the wireless device may be in coverage area of a firstcell of the base station and may not be in coverage area of a secondcell of the base station depending on the sizes of the first cell andthe second cell.

A base station in the RAN 104 may have various implementations. Forexample, a base station may be implemented by connecting a BBU (or a BBUpool) coupled to one or more RRHs and/or one or more relay nodes toextend the cell coverage. The BBU pool may be located at a centralizedsite like a cloud or data center. The BBU pool may be connected to aplurality of RRHs that control a plurality of cells. The combination ofBBU with the one or more RRHs may be referred to as a centralized orcloud RAN (C-RAN) architecture. In some implementations, the BBUfunctions may be implemented on virtual machines (VMs) on servers at acentralized location. This architecture may be referred to as virtualRAN (vRAN). All, most or a portion of the protocol layer functions(e.g., all or portions of physical layer, medium access control (MAC)layer and/or higher layers) may be implemented at the BBU pool and theprocessed data may be transmitted to the RRHs for further processingand/or RF transmission. The links between the BBU pool and the RRHs maybe referred to as fronthaul.

In some deployment scenarios, the RAN 104 may include macrocell basestations with high transmission power levels and large coverage areas.In other deployment scenarios, the RAN 104 may include base stationsthat employ different transmission power levels and/or have cells withdifferent coverage areas. For example, some base station may bemacrocell base stations with high transmission powers and/or largecoverage areas and other base station may be small cell base stationswith comparatively smaller transmission powers and/or coverage areas. Insome deployment scenarios, a small cell base station may have coveragethat is within or has overlap with coverage area of a macrocell basestation. A wireless device may communicate with the macrocell basestation while within the coverage area of the macrocell base station.For additional capacity, the wireless device may communicate with boththe macrocell base station and the small cell base station while in theoverlapped coverage area of the macrocell base station and the smallcell base station. Depending on their coverage areas, a small cell basestation may be referred to as a microcell base station, a picocell basestation, a femtocell base station or a home base station.

Different standard development organizations (SDOs) have specified, ormay specify in future, mobile communications systems that have similarcharacteristics as the mobile communications system 100 of FIG. 1A. Forexample, the Third-Generation Partnership Project (3GPP) is a group ofSDOs that provides specifications that define 3GPP technologies formobile communications systems that are akin to the mobile communicationssystem 100. The 3GPP has developed specifications for third generation(3G) mobile networks, fourth generation (4G) mobile networks and fifthgeneration (5G) mobile networks. The 3G, 4G and 5G networks are alsoknown as Universal Mobile Telecommunications System (UMTS), Long TermEvolution (LTE) and 5G system (5GS), respectively. In this disclosure,embodiments are described with respect to the RAN implemented in a 3GPP5G mobile network that is also referred to as next generation RAN(NG-RAN). The embodiments may also be implemented in other mobilecommunications systems such as 3G or 4G mobile networks or mobilenetworks that may be standardized in future such as sixth generation(6G) mobile networks or mobile networks that are implemented bystandards bodies other than 3GPP. The NG-RAN may be based on a new RATknown as new radio (NR) and/or other radio access technologies such asLTE and/or non-3GPP RATs.

FIG. 1B shows an example of a mobile communications system 110 inaccordance with several of various embodiments of the presentdisclosure. The mobile communications system 110 of FIG. 1B is anexample of a 5G mobile network and includes a 5G CN (5G-CN) 130, anNG-RAN 120 and UEs (collectively 112 and individually UE 112A and UE112B). The 5G-CN 130, the NG-RAN 120 and the UEs 112 of FIG. 1B operatesubstantially alike the CN 106, the RAN 104 and the at least onewireless device 102, respectively, as described for FIG. 1A.

The 5G-CN 130 of FIG. 1B connects the NG-RAN 120 to one or more externalnetworks (e.g., one or more data networks such as the Internet) and isresponsible for functions such as authentication, charging andend-to-end connection establishment. The 5G-CN has new enhancementscompared to previous generations of CNs (e.g., evolved packet core (EPC)in the 4G networks) including service-based architecture, support fornetwork slicing and control plane/user plane split. The service-basedarchitecture of the 5G-CN provides a modular framework based on serviceand functionalities provided by the core network wherein a set ofnetwork functions are connected via service-based interfaces. Thenetwork slicing enables multiplexing of independent logical networks(e.g., network slices) on the same physical network infrastructure. Forexample, a network slice may be for mobile broadband applications withfull mobility support and a different network slice may be fornon-mobile latency-critical applications such as industry automation.The control plane/user plane split enables independent scaling of thecontrol plane and the user plane. For example, the control planecapacity may be increased without affecting the user plane of thenetwork.

The 5G-CN 130 of FIG. 1B includes an access and mobility managementfunction (AMF) 132 and a user plane function (UPF) 134. The AMF 132 maysupport termination of non-access stratum (NAS) signaling, NAS signalingsecurity such as ciphering and integrity protection, inter-3GPP accessnetwork mobility, registration management, connection management,mobility management, access authentication and authorization andsecurity context management. The NAS is a functional layer between a UEand the CN and the access stratum (AS) is a functional layer between theUE and the RAN. The UPF 134 may serve as an interconnect point betweenthe NG-RAN and an external data network. The UPF may support packetrouting and forwarding, packet inspection and Quality of Service (QoS)handling and packet filtering. The UPF may further act as a ProtocolData Unit (PDU) session anchor point for mobility within and betweenRATs.

The 5G-CN 130 may include additional network functions (not shown inFIG. 1B) such as one or more Session Management Functions (SMFs), aPolicy Control Function (PCF), a Network Exposure Function (NEF), aUnified Data Management (UDM), an Application Function (AF), and/or anAuthentication Server Function (AUSF). These network functions alongwith the AMF 132 and UPF 134 enable a service-based architecture for the5G-CN.

The NG-RAN 120 may operate between the UEs 112 and the 5G-CN 130 and mayimplement one or more RATs. The NG-RAN 120 may include one or more gNBs(e.g., gNB 122A or gNB 122B or collectively gNBs 122) and/or one or moreng-eNBs (e.g., ng-eNB 124A or ng-eNB 124B or collectively ng-eNBs 124).The general terminology for gNB s 122 and/or an ng-eNBs 124 is a basestation and may be used interchangeably in this disclosure. The gNBs 122and the ng-eNBs 124 may include one or more antennas to communicate withthe UEs 112. The one or more antennas of the gNB s 122 or ng-eNBs 124may control one or more cells (or sectors) that provide radio coveragefor the UEs 112.

A gNB and/or an ng-eNB of FIG. 1B may be connected to the 5G-CN 130using an NG interface. A gNB and/or an ng-eNB may be connected withother gNBs and/or ng-eNBs using an Xn interface. The NG or the Xninterfaces are logical connections that may be established using anunderlying transport network. The interface between a UE and a gNB orbetween a UE and an ng-eNBs may be referred to as the Uu interface. Aninterface (e.g., Uu, NG or Xn) may be established by using a protocolstack that enables data and control signaling exchange between entitiesin the mobile communications system of FIG. 1B. When a protocol stack isused for transmission of user data, the protocol stack may be referredto as user plane protocol stack. When a protocol stack is used fortransmission of control signaling, the protocol stack may be referred toas control plane protocol stack. Some protocol layer may be used in bothof the user plane protocol stack and the control plane protocol stackwhile other protocol layers may be specific to the user plane or controlplane.

The NG interface of FIG. 1B may include an NG-User plane (NG-U)interface between a gNB and the UPF 134 (or an ng-eNB and the UPF 134)and an NG-Control plane (NG-C) interface between a gNB and the AMF 132(or an ng-eNB and the AMF 132). The NG-U interface may providenon-guaranteed delivery of user plane PDUs between a gNB and the UPF oran ng-eNB and the UPF. The NG-C interface may provide services such asNG interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer and/or warning message transmission.

The UEs 112 and a gNB may be connected using the Uu interface and usingthe NR user plane and control plane protocol stack. The UEs 112 and anng-eNB may be connected using the Uu interface using the LTE user planeand control plane protocol stack.

In the example mobile communications system of FIG. 1B, a 5G-CN isconnected to a RAN comprised of 4G LTE and/or 5G NR RATs. In otherexample mobile communications systems, a RAN based on the 5G NR RAT maybe connected to a 4G CN (e.g., EPC). For example, earlier releases of 5Gstandards may support a non-standalone mode of operation where a NRbased RAN is connected to the 4G EPC. In an example non-standalone mode,a UE may be connected to both a 5G NR gNB and a 4G LTE eNB (e.g., ang-eNB) and the control plane functionalities (such as initial access,paging and mobility) may be provided through the 4G LTE eNB. In astandalone of operation, the 5G NR gNB is connected to a 5G-CN and theuser plane and the control plane functionalities are provided by the 5GNR gNB.

FIG. 2A shows an example of the protocol stack for the user plan of anNR Uu interface in accordance with several of various embodiments of thepresent disclosure. The user plane protocol stack comprises fiveprotocol layers that terminate at the UE 200 and the gNB 210. The fiveprotocol layers, as shown in FIG. 2A, include physical (PHY) layerreferred to as PHY 201 at the UE 200 and PHY 211 at the gNB 210, mediumaccess control (MAC) layer referred to as MAC 202 at the UE 200 and MAC212 at the gNB 210, radio link control (RLC) layer referred to as RLC203 at the UE 200 and RLC 213 at the gNB 210, packet data convergenceprotocol (PDCP) layer referred to as PDCP 204 at the UE 200 and PDCP 214at the gNB 210, and service data application protocol (SDAP) layerreferred to as SDAP 205 at the UE 200 and SDAP 215 at the gNB 210. ThePHY layer, also known as layer 1 (L1), offers transport services tohigher layers. The other four layers of the protocol stack (MAC, RLC,PDCP and SDAP) are collectively known as layer 2 (L2).

FIG. 2B shows an example of the protocol stack for the control plan ofan NR Uu interface in accordance with several of various embodiments ofthe present disclosure. Some of the protocol layers (PHY, MAC, RLC andPDCP) are common between the user plane protocol stack shown in FIG. 2Aand the control plan protocol stack. The control plane protocol stackalso includes the RRC layer, referred to RRC 206 at the UE 200 and RRC216 at the gNB 210, that also terminates at the UE 200 and the gNB 210.In addition, the control plane protocol stack includes the NAS layerthat terminates at the UE 200 and the AMF 220. In FIG. 2B, the NAS layeris referred to as NAS 207 at the UE 200 and NAS 227 at the AMF 220.

FIG. 3 shows example functions and services offered to other layers by alayer in the NR user plane protocol stack of FIG. 2A in accordance withseveral of various embodiments of the present disclosure. For example,the SDAP layer of FIG. 3 (shown in FIG. 2A as SDAP 205 at the UE sideand SDAP 215 at the gNB side) may perform mapping and de-mapping of QoSflows to data radio bearers. The mapping and de-mapping may be based onQoS (e.g., delay, throughput, jitter, error rate, etc.) associated witha QoS flow. A QoS flow may be a QoS differentiation granularity for aPDU session which is a logical connection between a UE 200 and a datanetwork. A PDU session may contain one or more QoS flows. The functionsand services of the SDAP layer include mapping and de-mapping betweenone or more QoS flows and one or more data radio bearers. The SDAP layermay also mark the uplink and/or downlink packets with a QoS flow ID(QFI).

The PDCP layer of FIG. 3 (shown in FIG. 2A as PDCP 204 at the UE sideand PDCP 214 at the gNB side) may perform header compression anddecompression (e.g., using Robust Header Compression (ROHC) protocol) toreduce the protocol header overhead, ciphering and deciphering andintegrity protection and verification to enhance the security over theair interface, reordering and in-order delivery of packets anddiscarding of duplicate packets. A UE may be configured with one PDCPentity per bearer.

In an example scenario not shown in FIG. 3, a UE may be configured withdual connectivity and may connect to two different cell groups providedby two different base stations. For example, a base station of the twobase stations may be referred to as a master base station and a cellgroup provided by the master base station may be referred to as a mastercell group (MCG). The other base station of the two base stations may bereferred to as a secondary base station and the cell group provided bythe secondary base station may be referred to as a secondary cell group(SCG). A bearer may be configured for the UE as a split bearer that maybe handled by the two different cell groups. The PDCP layer may performrouting of packets corresponding to a split bearer to and/or from RLCchannels associated with the cell groups.

In an example scenario not shown in FIG. 3, a bearer of the UE may beconfigured (e.g., with control signaling) with PDCP packet duplication.A bearer configured with PDCP duplication may be mapped to a pluralityof RLC channels each corresponding to different one or more cells. ThePDCP layer may duplicate packets of the bearer configured with PDCPduplication and the duplicated packets may be mapped to the differentRLC channels. With PDCP packet duplication, the likelihood of correctreception of packets increases thereby enabling higher reliability.

The RLC layer of FIG. 3 (shown in FIG. 2A as RLC 203 at the UE side andRLC 213 at the gNB side) provides service to upper layers in the form ofRLC channels. The RLC layer may include three transmission modes:transparent mode (TM), Unacknowledged mode (UM) and Acknowledged mode(AM). The RLC layer may perform error correction through automaticrepeat request (ARQ) for the AM transmission mode, segmentation of RLCservice data units (SDUs) for the AM and UM transmission modes andre-segmentation of RLC SDUs for AM transmission mode, duplicatedetection for the AM transmission mode, RLC SDU discard for the AM andUM transmission modes, etc. The UE may be configured with one RLC entityper RLC channel.

The MAC layer of FIG. 3 (shown in FIG. 2A as MAC 202 at the UE side andMAC 212 at the gNB side) provides services to the RLC layer in form oflogical channels. The MAC layer may perform mapping between logicalchannels and transport channels, multiplexing/demultiplexing of MAC SDUsbelonging to one or more logical channels into/from transport blocks(TBs) delivered to/from the physical layer on transport channels,reporting of scheduling information, error correction through hybridautomatic repeat request (HARQ), priority handling between UEs by meansof dynamic scheduling, priority handling between logical channels of oneUE by means of logical channel prioritization and/or padding. In case ofcarrier aggregation, a MAC entity may comprise one HARQ entity per cell.A MAC entity may support multiple numerologies, transmission timings andcells. The control signaling may configure logical channels with mappingrestrictions. The mapping restrictions in logical channel prioritizationmay control the numerology(ies), cell(s), and/or transmissiontiming(s)/duration(s) that a logical channel may use.

The PHY layer of FIG. 3 (shown in FIG. 2A as PHY 201 at the UE side andPHY 211 at the gNB side) provides transport services to the MAC layer inform of transport channels. The physical layer may handlecoding/decoding, HARQ soft combining, rate matching of a coded transportchannel to physical channels, mapping of coded transport channels tophysical channels, modulation and demodulation of physical channels,frequency and time synchronization, radio characteristics measurementsand indication to higher layers, RF processing, and mapping to antennasand radio resources.

FIG. 4 shows example processing of packets at different protocol layersin accordance with several of various embodiments of the presentdisclosure. In this example, three Internet Protocol (IP) packets thatare processed by the different layers of the NR protocol stack. The termSDU shown in FIG. 4 is the data unit that is entered from/to a higherlayer. In contrast, a protocol data unit (PDU) is the data unit that isentered to/from a lower layer. The flow of packets in FIG. 4 is fordownlink. An uplink data flow through layers of the NR protocol stack issimilar to FIG. 4. In this example, the two leftmost IP packets aremapped by the SDAP layer (shown as SDAP 205 and SDAP 215 in FIG. 2A) toradio bearer 402 and the rightmost packet is mapped by the SDAP layer tothe radio bearer 404. The SDAP layer adds SDAP headers to the IP packetswhich are entered into the PDCP layer as PDCP SDUs. The PDCP layer isshown as PDCP 204 and PDCP 214 in FIG. 2A. The PDCP layer adds the PDCPheaders to the PDCP SDUs which are entered into the RLC layer as RLCSDUs. The RLC layer is shown as RLC 203 and RLC 213 in FIG. 2A. An RLCSDU may be segmented at the RLC layer. The RLC layer adds RLC headers tothe RLC SDUs after segmentation (if segmented) which are entered intothe MAC layer as MAC SDUs. The MAC layer adds the MAC headers to the MACSDUs and multiplexes one or more MAC SDUs to form a PHY SDU (alsoreferred to as a transport block (TB) or a MAC PDU).

In FIG. 4, the MAC SDUs are multiplexed to form a transport block. TheMAC layer may multiplex one or more MAC control elements (MAC CEs) withzero or more MAC SDUs to form a transport block. The MAC CEs may also bereferred to as MAC commands or MAC layer control signaling and may beused for in-band control signaling. The MAC CEs may be transmitted by abase station to a UE (e.g., downlink MAC CEs) or by a UE to a basestation (e.g., uplink MAC CEs). The MAC CEs may be used for transmissionof information useful by a gNB for scheduling (e.g., buffer statusreport (BSR) or power headroom report (PHR)), activation/deactivation ofone or more cells, activation/deactivation of configured radio resourcesfor or one or more processes, activation/deactivation of one or moreprocesses, indication of parameters used in one or more processes, etc.

FIG. 5A and FIG. 5B show example mapping between logical channels,transport channels and physical channels for downlink and uplink,respectively in accordance with several of various embodiments of thepresent disclosure. As discussed before, the MAC layer provides servicesto higher layer in the form of logical channels. A logical channel maybe classified as a control channel, if used for transmission of controland/or configuration information, or a traffic channel if used fortransmission of user data. Example logical channels in NR includeBroadcast Control Channel (BCCH) used for transmission of broadcastsystem control information, Paging Control Channel (PCCH) used forcarrying paging messages for wireless devices with unknown locations,Common Control Channel (CCCH) used for transmission of controlinformation between UEs and network and for UEs that have no RRCconnection with the network, Dedicated Control Channel (DCCH) which is apoint-to-point bi-directional channel for transmission of dedicatedcontrol information between a UE that has an RRC connection and thenetwork and Dedicated Traffic Channel (DTCH) which is point-to-pointchannel, dedicated to one UE, for the transfer of user information andmay exist in both uplink and downlink.

As discussed before, the PHY layer provides services to the MAC layerand higher layers in the form of transport channels. Example transportchannels in NR include Broadcast Channel (BCH) used for transmission ofpart of the BCCH referred to as master information block (MIB), DownlinkShared Channel (DL-SCH) used for transmission of data (e.g., from DTCHin downlink) and various control information (e.g., from DCCH and CCCHin downlink and part of the BCCH that is not mapped to the BCH), UplinkShared Channel (UL-SCH) used for transmission of uplink data (e.g., fromDTCH in uplink) and control information (e.g., from CCCH and DCCH inuplink) and Paging Channel (PCH) used for transmission of paginginformation from the PCCH. In addition, Random Access Channel (RACH) isa transport channel used for transmission of random access preambles.The RACH does not carry a transport block. Data on a transport channel(except RACH) may be organized in transport blocks, wherein One or moretransport blocks may be transmitted in a transmission time interval(TTI).

The PHY layer may map the transport channels to physical channels. Aphysical channel may correspond to time-frequency resources that areused for transmission of information from one or more transportchannels. In addition to mapping transport channels to physicalchannels, the physical layer may generate control information (e.g.,downlink control information (DCI) or uplink control information (UCI))that may be carried by the physical channels. Example DCI includescheduling information (e.g., downlink assignments and uplink grants),request for channel state information report, power control command,etc. Example UCI include HARQ feedback indicating correct or incorrectreception of downlink transport blocks, channel state informationreport, scheduling request, etc. Example physical channels in NR includea Physical Broadcast Channel (PBCH) for carrying information from theBCH, a Physical Downlink Shared Channel (PDSCH) for carrying informationform the PCH and the DL-SCH, a Physical Downlink Control Channel (PDCCH)for carrying DCI, a Physical Uplink Shared Channel (PUSCH) for carryinginformation from the UL-SCH and/or UCI, a Physical Uplink ControlChannel (PUCCH) for carrying UCI and Physical Random Access Channel(PRACH) for transmission of RACH (e.g., random access preamble).

The PHY layer may also generate physical signals that are not originatedfrom higher layers. As shown in FIG. 5A, example downlink physicalsignals include Demodulation Reference Signal (DM-RS), Phase TrackingReference Signal (PT-RS), Channel State Information Reference Signal(CSI-RS), Primary Synchronization Signal (PSS) and SecondarySynchronization Signal (SSS). As shown in FIG. 5B, example uplinkphysical signals include DM-RS, PT-RS and sounding reference signal(SRS).

As indicated earlier, some of the protocol layers (PHY, MAC, RLC andPDCP) of the control plane of an NR Uu interface, are common between theuser plane protocol stack (as shown in FIG. 2A) and the control planeprotocol stack (as shown in FIG. 2B). In addition to PHY, MAC, RLC andPDCP, the control plane protocol stack includes the RRC protocol layerand the NAS protocol layer.

The NAS layer, as shown in FIG. 2B, terminates at the UE 200 and the AMF220 entity of the 5G-C 130. The NAS layer is used for core networkrelated functions and signaling including registration, authentication,location update and session management. The NAS layer uses services fromthe AS of the Uu interface to transmit the NAS messages.

The RRC layer, as shown in FIG. 2B, operates between the UE 200 and thegNB 210 (more generally NG-RAN 120) and may provide services andfunctions such as broadcast of system information (SI) related to AS andNAS as well as paging initiated by the 5G-C 130 or NG-RAN 120. Inaddition, the RRC layer is responsible for establishment, maintenanceand release of an RRC connection between the UE 200 and the NG-RAN 120,carrier aggregation configuration (e.g., addition, modification andrelease), dual connectivity configuration (e.g., addition, modificationand release), security related functions, radio bearerconfiguration/maintenance and release, mobility management (e.g.,maintenance and context transfer), UE cell selection and reselection,inter-RAT mobility, QoS management functions, UE measurement reportingand control, radio link failure (RLF) detection and NAS messagetransfer. The RRC layer uses services from PHY, MAC, RLC and PDCP layersto transmit RRC messages using signaling radio bearers (SRBs). The SRBsare mapped to CCCH logical channel during connection establishment andto DCCH logical channel after connection establishment.

FIG. 6 shows example physical layer processes for signal transmission inaccordance with several of various embodiments of the presentdisclosure. Data and/or control streams from MAC layer may beencoded/decoded to offer transport and control services over the radiotransmission link. For example, one or more (e.g., two as shown in FIG.6) transport blocks may be received from the MAC layer for transmissionvia a physical channel (e.g., a physical downlink shared channel or aphysical uplink shared channel). A cyclic redundancy check (CRC) may becalculated and attached to a transport block in the physical layer. TheCRC calculation may be based on one or more cyclic generatorpolynomials. The CRC may be used by the receiver for error detection.Following the transport block CRC attachment, a low-density parity check(LDPC) base graph selection may be performed. In example embodiments,two LDPC base graphs may be used wherein a first LDPC base graph may beoptimized for small transport blocks and a second LDPC base graph may beoptimized for comparatively larger transport blocks.

The transport block may be segmented into code blocks and code block CRCmay be calculated and attached to a code block. A code block may be LDPCcoded and the LDPC coded blocks may be individually rate matched. Thecode blocks may be concatenated to create one or more codewords. Thecontents of a codeword may be scrambled and modulated to generate ablock of complex-valued modulation symbols. The modulation symbols maybe mapped to a plurality of transmission layers (e.g., multiple-inputmultiple-output (MIMO) layers) and the transmission layers may besubject to transform precoding and/or precoding. The precodedcomplex-valued symbols may be mapped to radio resources (e.g., resourceelements). The signal generator block may create a baseband signal andup-convert the baseband signal to a carrier frequency for transmissionvia antenna ports. The signal generator block may employ mixers, filtersand/or other radio frequency (RF) components prior to transmission viathe antennas. The functions and blocks in FIG. 6 are illustrated asexamples and other mechanisms may be implemented in various embodiments.

FIG. 7 shows examples of RRC states and RRC state transitions at a UE inaccordance with several of various embodiments of the presentdisclosure. A UE may be in one of three RRC states: RRC_IDLE 702,RRC_INACTIVE 704 and RRC_CONNECTED 706. In RRC_IDLE 702 state, no RRCcontext (e.g., parameters needed for communications between the UE andthe network) may be established for the UE in the RAN. In RRC_IDLE 702state, no data transfer between the UE and the network may take placeand uplink synchronization is not maintained. The wireless device maysleep most of the time and may wake up periodically to receive pagingmessages. The uplink transmission of the UE may be based on a randomaccess process and to enable transition to the RRC_CONNECTED 706 state.The mobility in RRC_IDLE 702 state is through a cell reselectionprocedure where the UE camps on a cell based on one or more criteriaincluding signal strength that is determined based on the UEmeasurements.

In RRC_CONNECTED 706 state, the RRC context is established and both theUE and the RAN have necessary parameters to enable communicationsbetween the UE and the network. In the RRC_CONNECTED 706 state, the UEis configured with an identity known as a Cell Radio Network TemporaryIdentifier (C-RNTI) that is used for signaling purposes (e.g., uplinkand downlink scheduling, etc.) between the UE and the RAN. The wirelessdevice mobility in the RRC_CONNECTED 706 state is managed by the RAN.The wireless device provides neighboring cells and/or current servingcell measurements to the network and the network may make hand overdecisions. Based on the wireless device measurements, the currentserving base station may send a handover request message to aneighboring base station and may send a handover command to the wirelessdevice to handover to a cell of the neighboring base station. Thetransition of the wireless device from the RRC IDLE 702 state to the RRCCONNECTED 706 state or from the RRC_CONNECTED 706 state to the RRC_IDLE702 state may be based on connection establishment and connectionrelease procedures (shown collectively as connectionestablishment/release 710 in FIG. 7).

To enable a faster transition to the RRC_CONNECTED 706 state (e.g.,compared to transition from RRC_IDLE 702 state to RRC_CONNECTED 706state), an RRC_INACTIVE 704 state is used for an NR UE wherein, the RRCcontext is kept at the UE and the RAN. The transition from theRRC_INACTIVE 704 state to the RRC_CONNECTED 706 state is handled by RANwithout CN signaling. Similar to the RRC_IDLE 702 state, the mobility inRRC_INACTIVE 704 state is based on a cell reselection procedure withoutinvolvement from the network. The transition of the wireless device fromthe RRC_INACTIVE 704 state to the RRC CONNECTED 706 state or from theRRC_CONNECTED 706 state to the RRC_INACTIVE 704 state may be based onconnection resume and connection inactivation procedures (showncollectively as connection resume/inactivation 712 in FIG. 7). Thetransition of the wireless device from the RRC_INACTIVE 704 state to theRRC_IDLE 702 state may be based on a connection release 714 procedure asshown in FIG. 7.

In NR, Orthogonal Frequency Division Multiplexing (OFDM), also calledcyclic prefix OFDM (CP-OFDM), is the baseline transmission scheme inboth downlink and uplink of NR and the Discrete Fourier Transform (DFT)spread OFDM (DFT-s-OFDM) is a complementary uplink transmission inaddition to the baseline OFDM scheme. OFDM is multi-carrier transmissionscheme wherein the transmission bandwidth may be composed of severalnarrowband sub-carriers. The subcarriers are modulated by the complexvalued OFDM modulation symbols resulting in an OFDM signal. The complexvalued OFDM modulation symbols are obtained by mapping, by a modulationmapper, the input data (e.g., binary digits) to different points of amodulation constellation diagram. The modulation constellation diagramdepends on the modulation scheme. NR may use different types ofmodulation schemes including Binary Phase Shift Keying (BPSK), π/2-BPSK,Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation(16QAM), 64QAM and 256QAM. Different and/or higher order modulationschemes (e.g., M-QAM in general) may be used. An OFDM signal with Nsubcarriers may be generated by processing N subcarriers in parallel forexample by using Inverse Fast Fourier Transform (IFFT) processing. TheOFDM receiver may use FFT processing to recover the transmitted OFDMmodulation symbols. The subcarrier spacing of subcarriers in an OFDMsignal is inversely proportional to an OFDM modulation symbol duration.For example, for a 15 KHz subcarrier spacing, duration of an OFDM signalis nearly 66.7 μs. To enhance the robustness of OFDM transmission intime dispersive channels, a cyclic prefix (CP) may be inserted at thebeginning of an OFDM symbol. For example, the last part of an OFDMsymbol may be copied and inserted at the beginning of an OFDM symbol.The CP insertion enhanced the OFDM transmission scheme by preservingsubcarrier orthogonality in time dispersive channels.

In NR, different numerologies may be used for OFDM transmission. Anumerology of OFDM transmission may indicate a subcarrier spacing and aCP duration for the OFDM transmission. For example, a subcarrier spacingin NR may generally be a multiple of 15 KHz and expressed as Δf=2^(μ).15 KHz (μ=0, 1, 2, . . . ). Example subcarrier spacings used in NRinclude 15 KHz (μ=0), 30 KHz (μ=1), 60 KHz (μ=2), 120 KHz (μ=3) and 240KHz (μ=4). As discussed before, a duration of OFDM symbol is inverselyproportional to the subcarrier spacing and therefor OFDM symbol durationmay depend on the numerology (e.g. the μ value).

FIG. 8 shows an example time domain transmission structure in NR whereinOFDM symbols are grouped into slots, subframes and frames in accordancewith several of various embodiments of the present disclosure. A slot isa group of N_(symb) ^(slot) OFDM symbols, wherein the N_(symb) ^(slot)may have a constant value (e.g., 14). Since different numerologiesresults in different OFDM symbol durations, duration of a slot may alsodepend on the numerology and may be variable. A subframe may have aduration of 1 ms and may be composed of one or more slots, the number ofwhich may depend on the slot duration. The number of slots per subframeis therefore a function of μ and may generally expressed as N_(slot)^(subframe,μ) and the number of symbols per subframe may be expressed asN_(symb) ^(subframe,μ)=N_(symb) ^(slot)N_(slot) ^(subframe,μ). A framemay have a duration of 10 ms and may consist of 10 subframes. The numberof slots per frame may depend on the numerology and therefore may bevariable. The number of slots per frame may generally be expressed asN_(slot) ^(frame,μ).

An antenna port may be defined as a logical entity such that channelcharacteristics over which a symbol on the antenna port is conveyed maybe inferred from the channel characteristics over which another symbolon the same antenna port is conveyed. For example, for DM-RS associatedwith a PDSCH, the channel over which a PDSCH symbol on an antenna portis conveyed may be inferred from the channel over which a DM-RS symbolon the same antenna port is conveyed, for example, if the two symbolsare within the same resource as the scheduled PDSCH and/or in the sameslot and/or in the same precoding resource block group (PRG). Forexample, for DM-RS associated with a PDCCH, the channel over which aPDCCH symbol on an antenna port is conveyed may be inferred from thechannel over which a DM-RS symbol on the same antenna port is conveyedif, for example, the two symbols are within resources for which the UEmay assume the same precoding being used. For example, for DM-RSassociated with a PBCH, the channel over which a PBCH symbol on oneantenna port is conveyed may be inferred from the channel over which aDM-RS symbol on the same antenna port is conveyed if, for example, thetwo symbols are within a SS/PBCH block transmitted within the same slot,and with the same block index. The antenna port may be different from aphysical antenna. An antenna port may be associated with an antenna portnumber and different physical channels may correspond to differentranges of antenna port numbers.

FIG. 9 shows an example of time-frequency resource grid in accordancewith several of various embodiments of the present disclosure. Thenumber of subcarriers in a carrier bandwidth may be based on thenumerology of OFDM transmissions in the carrier. A resource element,corresponding to one symbol duration and one subcarrier, may be thesmallest physical resource in the time-frequency grid. A resourceelement (RE) for antenna port p and subcarrier spacing configuration μmay be uniquely identified by (k,l)_(p,μ) where k is the index of asubcarrier in the frequency domain and 1 may refer to the symbolposition in the time domain relative to some reference point. A resourceblock may be defined as N_(SC) ^(RB)=12 subcarriers. Since subcarrierspacing depends on the numerology of OFDM transmission, the frequencydomain span of a resource block may be variable and may depend on thenumerology. For example, for a subcarrier spacing of 15 KHz (e.g., μ=0),a resource block may be 180 KHz and for a subcarrier spacing of 30 KHz(e.g., μ=1), a resource block may be 360 KHz.

With large carrier bandwidths defined in NR and due to limitedcapabilities for some UEs (e.g., due to hardware limitations), a UE maynot support an entire carrier bandwidth. Receiving on the full carrierbandwidth may imply high energy consumption. For example, transmittingdownlink control channels on the full downlink carrier bandwidth mayresult in high power consumption for wide carrier bandwidths. NR may usea bandwidth adaptation procedure to dynamically adapt the transmit andreceive bandwidths. The transmit and receive bandwidth of a UE on a cellmay be smaller than the bandwidth of the cell and may be adjusted. Forexample, the width of the transmit and/or receive bandwidth may change(e.g., shrink during period of low activity to save power); the locationof the transmit and/or receive bandwidth may move in the frequencydomain (e.g., to increase scheduling flexibility); and the subcarrierspacing of the transmit or receive bandwidth may change (e.g., to allowdifferent services). A subset of the cell bandwidth may be referred toas a Bandwidth Part (BWP) and bandwidth adaptation may be achieved byconfiguring the UE with one or more BWPs. The base station may configurea UE with a set of downlink BWPs and a set of uplink BWPs. A BWP may becharacterized by a numerology (e.g., subcarrier spacing and cyclicprefix) and a set of consecutive resource blocks in the numerology ofthe BWP. One or more first BWPs of the one or more BWPs of the cell maybe active at a time. An active BWP may be an active downlink BWP or anactive uplink BWP.

FIG. 10 shows an example of bandwidth part adaptation and switching. Inthis example, three BWPs (BWP₁ 1004, BWP₂ 1006 and BWP₃ 1008) areconfigured for a UE on a carrier bandwidth. The BWP₁ is configured witha bandwidth of 40 MHz and a numerology with subcarrier spacing of 15KHz, the BWP₂ is configured with a bandwidth of 10 MHz and a numerologywith subcarrier spacing of 15 KHz and the BWP₃ is configured with abandwidth of 20 MHz and a subcarrier spacing of 60 KHz. The wirelessdevice may switch from a first BWP (e.g., BWP₁) to a second BWP (e.g.,BWP₂). An active BWP of the cell may change from the first BWP to thesecond BWP in response to the BWP switching.

The BWP switching (e.g., BWP switching 1010, BWP switching 1012, BWPswitching 1014, or BWP switching 1016 in FIG. 10) may be based on acommand from the base station. The command may be a DCI comprisingscheduling information for the UE in the second BWP. In case of uplinkBWP switching, the first BWP and the second BWP may be uplink BWPs andthe scheduling information may be an uplink grant for uplinktransmission via the second BWP. In case of downlink BWP switching, thefirst BWP and the second BWP may be downlink BWPs and the schedulinginformation may be a downlink assignment for downlink reception via thesecond BWP.

The BWP switching (e.g., BWP switching 1010, BWP switching 1012, BWPswitching 1014, or BWP switching 1016 in FIG. 10) may be based on anexpiry of a timer. The base station may configure a wireless device witha BWP inactivity timer and the wireless device may switch to a defaultBWP (e.g., default downlink BWP) based on the expiry of the BWPinactivity timer. The expiry of the BWP inactivity timer may be anindication of low activity on the current active downlink BWP. The basestation may configure the wireless device with the default downlink BWP.If the base station does not configure the wireless device with thedefault BWP, the default BWP may be an initial downlink BWP. The initialactive BWP may be the BWP that the wireless device receives schedulinginformation for remaining system information upon transition to anRRC_CONNECTED state.

A wireless device may monitor a downlink control channel of a downlinkBWP. For example, the UE may monitor a set of PDCCH candidates inconfigured monitoring occasions in one or more configured COntrolREsource SETs (CORESETs) according to the corresponding search spaceconfigurations. A search space configuration may define how/where tosearch for PDCCH candidates. For example, the search space configurationparameters may comprise a monitoring periodicity and offset parameterindicating the slots for monitoring the PDCCH candidates. The searchspace configuration parameters may further comprise a parameterindicating a first symbol with a slot within the slots determined formonitoring PDCCH candidates. A search space may be associated with oneor more CORESETs and the search space configuration may indicate one ormore identifiers of the one or more CORESETs. The search spaceconfiguration parameters may further indicate that whether the searchspace is a common search space or a UE-specific search space. A commonsearch space may be monitored by a plurality of wireless devices and aUE-specific search space may be dedicated to a specific UE.

FIG. 11A shows example arrangements of carriers in carrier aggregationin accordance with several of various embodiments of the presentdisclosure. With carrier aggregation, multiple NR component carriers(CCs) may be aggregated. Downlink transmissions to a wireless device maytake place simultaneously on the aggregated downlink CCs resulting inhigher downlink data rates. Uplink transmissions from a wireless devicemay take place simultaneously on the aggregated uplink CCs resulting inhigher uplink data rates. The component carriers in carrier aggregationmay be on the same frequency band (e.g., intra-band carrier aggregation)or on different frequency bands (e.g., inter-band carrier aggregation).The component carriers may also be contiguous or non-contiguous. Thisresults in three possible carrier aggregation scenarios, intra-bandcontiguous CA 1102, intra-band non-contiguous CA 1104 and inter-band CA1106 as shown in FIG. 11A. Depending on the UE capability for carrieraggregation, a UE may transmit and/or receive on multiple carriers orfor a UE that is not capable of carrier aggregation, the UE may transmitand/or receive on one component carrier at a time. In this disclosure,the carrier aggregation is described using the term cell and a carrieraggregation capable UE may transmit and/or receive via multiple cells.

In carrier aggregation, a UE may be configured with multiple cells. Acell of the multiple cells configured for the UE may be referred to as aPrimary Cell (PCell). The PCell may be the first cell that the UE isinitially connected to. One or more other cells configured for the UEmay be referred to as Secondary Cells (SCells). The base station mayconfigure a UE with multiple SCells. The configured SCells may bedeactivated upon configuration and the base station may dynamicallyactivate or deactivate one or more of the configured SCells based ontraffic and/or channel conditions. The base station may activate ordeactivate configured SCells using a SCell Activation/Deactivation MACCE. The SCell Activation/Deactivation MAC CE may comprise a bitmap,wherein each bit in the bitmap may correspond to a SCell and the valueof the bit indicates an activation status or deactivation status of theSCell.

An SCell may also be deactivated in response to expiry of a SCelldeactivation timer of the SCell. The expiry of an SCell deactivationtimer of an SCell may be an indication of low activity (e.g., lowtransmission or reception activity) on the SCell. The base station mayconfigure the SCell with an SCell deactivation timer. The base stationmay not configure an SCell deactivation timer for an SCell that isconfigured with PUCCH (also referred to as a PUCCH SCell). Theconfiguration of the SCell deactivation timer may be per configuredSCell and different SCells may be configured with different SCelldeactivation timer values. The SCell deactivation timer may be restartedbased on one or more criteria including reception of downlink controlinformation on the SCell indicating uplink grant or downlink assignmentfor the SCell or reception of downlink control information on ascheduling cell indicating uplink grant or downlink assignment for theSCell or transmission of a MAC PDU based on a configured uplink grant orreception of a configured downlink assignment.

A PCell for a UE may be an SCell for another UE and a SCell for a UE maybe PCell for another UE. The configuration of PCell may be UE-specific.One or more SCells of the multiple SCells configured for a UE may beconfigured as downlink-only SCells, e.g., may only be used for downlinkreception and may not be used for uplink transmission. In case ofself-scheduling, the base station may transmit signaling for uplinkgrants and/or downlink assignments on the same cell that thecorresponding uplink or downlink transmission takes place. In case ofcross-carrier scheduling, the base station may transmit signaling foruplink grants and/or downlink assignments on a cell different from thecell that the corresponding uplink or downlink transmission takes place.

FIG. 11B shows examples of uplink control channel groups in accordancewith several of various embodiments of the present disclosure. A basestation may configure a UE with multiple PUCCH groups wherein a PUCCHgroup comprises one or more cells. For example, as shown in FIG. 11B,the base station may configure a UE with a primary PUCCH group 1114 anda secondary PUCCH group 1116. The primary PUCCH group may comprise thePCell 1110 and one or more first SCells. First UCI corresponding to thePCell and the one or more first SCells of the primary PUCCH group may betransmitted by the PUCCH of the PCell. The first UCI may be, forexample, HARQ feedback for downlink transmissions via downlink CCs ofthe PCell and the one or more first SCells. The secondary PUCCH groupmay comprise a PUCCH SCell and one or more second SCells. Second UCIcorresponding to the PUCCH SCell and the one or more second SCells ofthe secondary PUCCH group may be transmitted by the PUCCH of the PUCCHSCell. The second UCI may be, for example, HARQ feedback for downlinktransmissions via downlink CCs of the PUCCH SCell and the one or moresecond SCells.

FIG. 12A, FIG. 12B and FIG. 12C show example random access processes inaccordance with several of various embodiments of the presentdisclosure. FIG. 12A shows an example of four step contention-basedrandom access (CBRA) procedure. The four-step CBRA procedure includesexchanging four messages between a UE and a base station. Msg1 may befor transmission (or retransmission) of a random access preamble by thewireless device to the base station. Msg2 may be the random accessresponse (RAR) by the base station to the wireless device. Msg3 is thescheduled transmission based on an uplink grant indicated in Msg2 andMsg4 may be for contention resolution.

The base station may transmit one or more RRC messages comprisingconfiguration parameters of the random access parameters. The randomaccess parameters may indicate radio resources (e.g., time-frequencyresources) for transmission of the random access preamble (e.g., Msg1),configuration index, one or more parameters for determining the power ofthe random access preamble (e.g., a power ramping parameter, a preamblereceived target power, etc.), a parameter indicating maximum number ofpreamble transmission, RAR window for monitoring RAR, cell-specificrandom access parameters and UE specific random access parameters. TheUE-specific random access parameters may indicate one or more PRACHoccasions for random access preamble (e.g., Msg1) transmissions. Therandom access parameters may indicate association between the PRACHoccasions and one or more reference signals (e.g., SSB or CSI-RS). Therandom access parameters may further indicate association between therandom access preambles and one or more reference signals (e.g., SBB orCSI-RS). The UE may use one or more reference signals (e.g., SSB(s) orCSI-RS(s)) and may determine a random access preamble to use for Msg1transmission based on the association between the random accesspreambles and the one or more reference signals. The UE may use one ormore reference signals (e.g., SSB(s) or CSI-RS(s)) and may determine thePRACH occasion to use for Msg1 transmission based on the associationbetween the PRACH occasions and the reference signals. The UE mayperform a retransmission of the random access preamble if no response isreceived with the RAR window following the transmission of the preamble.UE may use a higher transmission power for retransmission of thepreamble. UE may determine the higher transmission power of the preamblebased on the power ramping parameter.

Msg2 is for transmission of RAR by the base station. Msg2 may comprise aplurality of RARs corresponding to a plurality of random accesspreambles transmitted by a plurality of UEs. Msg2 may be associated witha random access temporary radio identifier (RA-RNTI) and may be receivedin a common search space of the UE. The RA-RNTI may be based on thePRACH occasion (e.g., time and frequency resources of a PRACH) in whicha random access preamble is transmitted. RAR may comprise a timingadvance command for uplink timing adjustment at the UE, an uplink grantfor transmission of Msg3 and a temporary C-RNTI. In response to thesuccessful reception of Msg2, the UE may transmit the Msg3. Msg3 andMsg4 may enable contention resolution in case of CBRA. In a CBRA, aplurality of UEs may transmit the same random access preamble and mayconsider the same RAR as being corresponding to them. UE may include adevice identifier in Msg3 (e.g., a C-RNTI, temporary C-RNTI or other UEidentity). Base station may transmit the Msg4 with a PDSCH and UE mayassume that the contention resolution is successful in response to thePDSCH used for transmission of Msg4 being associated with the UEidentifier included in Msg3.

FIG. 12B shows an example of a contention-free random access (CFRA)process. Msg 1 (random access preamble) and Msg 2 (random accessresponse) in FIG. 12B for CFRA may be analogous to Msg 1 and Msg 2 inFIG. 12A for CBRA. In an example, the CFRA procedure may be initiated inresponse to a PDCCH order from a base station. The PDCCH order forinitiating the CFRA procedure by the wireless device may be based on aDCI having a first format (e.g., format 1_0). The DCI for the PDCCHorder may comprise a random access preamble index, an UL/SUL indicatorindicating an uplink carrier of a cell (e.g., normal uplink carrier orsupplementary uplink carrier) for transmission of the random accesspreamble, a SS/PBCH index indicating the SS/PBCH that may be used todetermine a RACH occasion for PRACH transmission, a PRACH mask indexindicating the RACH occasion associated with the SS/PBCH indicated bythe SS/PBCH index for PRACH transmission, etc. In an example, the CFRAprocess may be started in response to a beam failure recovery process.The wireless device may start the CFRA for the beam failure recoverywithout a command (e.g., PDCCH order) from the base station and by usingthe wireless device dedicated resources.

FIG. 12C shows an example of a two-step random access process comprisingtwo messages exchanged between a wireless device and a base station. MsgA may be transmitted by the wireless device to the base station and maycomprise one or more transmissions of a preamble and/or one or moretransmissions of a transport block. The transport block in Msg A and Msg3 in FIG. 12A may have similar and/or equivalent contents. The transportblock of Msg A may comprise data and control information (e.g., SR, HARQfeedback, etc.). In response to the transmission of Msg A, the wirelessdevice may receive Msg B from the base station. Msg B in FIG. 12C andMsg 2 (e.g., RAR) illustrated in FIGS. 12A and 12B may have similarand/or equivalent content.

The base station may periodically transmit synchronization signals(SSs), e.g., primary SS (PSS) and secondary SS (SSS) along with PBCH oneach NR cell. The PSS/SSS together with PBCH is jointly referred to as aSS/PBCH block. The SS/PBCH block enables a wireless device to find acell when entering to the mobile communications network or find newcells when moving within the network. The SS/PBCH block spans four OFDMsymbols in time domain. The PSS is transmitted in the first symbol andoccupies 127 subcarriers in frequency domain. The SSS is transmitted inthe third OFDM symbol and occupies the same 127 subcarriers as the PSS.There are eight and nine empty subcarriers on each side of the SSS. ThePBCH is transmitted on the second OFDM symbol occupying 240 subcarriers,the third OFDM symbol occupying 48 subcarriers on each side of the SSS,and on the fourth OFDM symbol occupying 240 subcarriers. Some of thePBCH resources indicated above may be used for transmission of thedemodulation reference signal (DMRS) for coherent demodulation of thePBCH. The SS/PBCH block is transmitted periodically with a periodranging from 5 ms to 160 ms. For initial cell search or for cell searchduring inactive/idle state, a wireless device may assume that that theSS/PBCH block is repeated at least every 20 ms.

In NR, transmissions using of antenna arrays, with many antennaelements, and beamforming plays an important role specially in higherfrequency bands. Beamforming enables higher capacity by increasing thesignal strength (e.g., by focusing the signal energy in a specificdirection) and by lowering the amount interference received at thewireless devices. The beamforming techniques may generally be divided toanalog beamforming and digital beamforming techniques. With digitalbeamforming, signal processing for beamforming is carried out in thedigital domain before digital-to-analog conversion and detailed controlof both amplitude and phase of different antenna elements may bepossible. With analog beamforming, the signal processing for beamformingis carried out in the analog domain and after the digital to analogconversion. The beamformed transmissions may be in one direction at atime. For example, the wireless devices that are in different directionsrelative to the base station may receive their downlink transmissions atdifferent times. For analog receiver-side beamforming, the receiver mayfocus its receiver beam in one direction at a time.

In NR, the base station may use beam sweeping for transmission ofSS/PBCH blocks. The SS/PBCH blocks may be transmitted in different beamsusing time multiplexing. The set of SS/PBCH blocks that are transmittedin one beam sweep may be referred to as a SS/PBCH block set. The periodof PBCH/SSB block transmission may be a time duration between a SS/PBCHblock transmission in a beam and the next SS/PBCH block transmission inthe same beam. The period of SS/PBCH block is, therefore, also theperiod of the SS/PBCH block set.

FIG. 13A shows example time and frequency structure of SS/PBCH blocksand their associations with beams in accordance with several of variousembodiments of the present disclosure. In this example, a SS/PBCH block(also referred to as SSB) set comprise L SSBs wherein an SSB in the SSBset is associated with (e.g., transmitted in) one of L beams of a cell.The transmission of SBBs of an SSB set may be confined within a 5 msinterval, either in a first half-frame or a second half-frame of a 10 msframe. The number of SSBs in an SSB set may depend on the frequency bandof operation. For example, the number of SSBs in a SSB set may be up tofour SSBs in frequency bands below 3 GHz enabling beam sweeping of up tofour beams, up to eight SSBs in frequency bands between 3 GHz and 6 GHzenabling beam sweeping of up to eight beams, and up to sixty four SSBsin higher frequency bands enabling beam sweeping of up to sixty fourbeams. The SSs of an SSB may depend on a physical cell identity (PCI) ofthe cell and may be independent of which beam of the cell is used fortransmission of the SSB. The PBCH of an SSB may indicate a time indexparameter and the wireless device may determine the relative position ofthe SSB within the SSB set using the time index parameter. The wirelessdevice may use the relative position of the SSB within an SSB set fordetermining the frame timing and/or determining RACH occasions for arandom access process.

A wireless device entering the mobile communications network may firstsearch for the PSS. After detecting the PSS, the wireless device maydetermine the synchronization up to the periodicity of the PSS. Bydetecting the PSS, the wireless device may determine the transmissiontiming of the SSS. The wireless device may determine the PCI of the cellafter detecting the SSS. The PBCH of a SS/PBCH block is a downlinkphysical channel that carries the MIB. The MIB may be used by thewireless device to obtain remaining system information (RMSI) that isbroadcast by the network. The RMSI may include System Information Block1 (SIB1) that contains information required for the wireless device toaccess the cell.

As discussed earlier, the wireless device may determine a time indexparameter from the SSB. The PBCH comprises a half-frame parameterindicating whether the SSB is in the first 5 ms half or the second 5 mshalf of a 10 ms frame. The wireless device may determine the frameboundary using the time index parameter and the half-frame parameter. Inaddition, the PBCH may comprise a parameter indicating the system framenumber (SFN) of the cell.

The base station may transmit CSI-RS and a UE may measure the CSI-RS toobtain channel state information (CSI). The base station may configurethe CSI-RS in a UE-specific manner. In some scenarios, same set ofCSI-RS resources may be configured for multiple UEs and one or moreresource elements of a CSI-RS resource may be shared among multiple UEs.A CSI-RS resource may be configured such that it does not collide with aCORESET configured for the wireless device and/or with a DMRS of a PDSCHscheduled for the wireless device and/or transmitted SSBs. The UE maymeasure one or more CSI-RSs configured for the UE and may generate a CSIreport based on the CSI-RS measurements and may transmit the CSI reportto the base station for scheduling, link adaptation and/or otherpurposes.

NR supports flexible CSI-RS configurations. A CSI-RS resource may beconfigured with single or multiple antenna ports and with configurabledensity. Based on the number of configured antenna ports, a CSI-RSresource may span different number of OFDM symbols (e.g., 1, 2, and 4symbols). The CSI-RS may be configured for a downlink BWP and may usethe numerology of the downlink BWP. The CSI-RS may be configured tocover the full bandwidth of the downlink BWP or a portion of thedownlink BWP. In some case, the CSI-RS may be repeated in every resourceblock of the CSI-RS bandwidth, referred to as CSI-RS with density equalto one. In some cases, the CSI-RS may be configured to be repeated inevery other resource block of the CSI-RS bandwidth. CSI-RS may benon-zero power (NZP) CSI-RS or zero-power (ZP) CSI-RS.

The base station may configure a wireless device with one or more setsof NZP CSI-RS resources. The base station may configure the wirelessdevice with a NZP CSI-RS resource set using an RRC information element(IE) NZP-CSI-RS-ResourceSet indicating a NZP CSI-RS resource setidentifier (ID) and parameters specific to the NZP CSI-RS resource set.An NZP CSI-RS resource set may comprise one or more CSI-RS resources. AnNZP CSI-RS resource set may be configured as part of the CSI measurementconfiguration.

The CSI-RS may be configured for periodic, semi-persistent or aperiodictransmission. In case of the periodic and semi-persistent CSI-RSconfigurations, the wireless device may be configured with a CSIresource periodicity and offset parameter that indicate a periodicityand corresponding offset in terms of number of slots. The wirelessdevice may determine the slots that the CSI-RSs are transmitted. Forsemi-persistent CSI-RS, the CSI-RS resources for CSI-RS transmissionsmay be activated and deactivated by using a semi-persistent (SP) CSI-CSIResource Set Activation/Deactivation MAC CE. In response to receiving aMAC CE indicating activation of semi-persistent CSI-RS resources, thewireless device may assume that the CSI-RS transmissions will continueuntil the CSI-RS resources for CSI-RS transmissions are activated.

As discussed before, CSI-RS may be configured for a wireless device asNZP CSI-RS or ZP CSI-RS. The configuration of the ZP CSI-RS may besimilar to the NZP CSI-RS with the difference that the wireless devicemay not carry out measurements for the ZP CSI-RS. By configuring ZPCSI-RS, the wireless device may assume that a scheduled PDSCH thatincludes resource elements from the ZP CSI-RS is rate matched aroundthose ZP CSI-RS resources. For example, a ZP CSI-RS resource configuredfor a wireless device may be an NZP CSI-RS resource for another wirelessdevice. For example, by configuring ZP CSI-RS resources for the wirelessdevice, the base station may indicate to the wireless device that thePDSCH scheduled for the wireless device is rate matched around the ZPCSI-RS resources.

A base station may configure a wireless device with channel stateinformation interference measurement (CSI-IM) resources. Similar to theCSI-RS configuration, configuration of locations and density of CSI-IMresources may be flexible. The CSI-IM resources may be periodic(configured with a periodicity), semi-persistent (configured with aperiodicity and activated and deactivated by MAC CE) or aperiodic(triggered by a DCI).

Tracking reference signals (TRSs) may be configured for a wirelessdevice as a set of sparse reference signals to assist the wireless intime and frequency tracking and compensating time and frequencyvariations in its local oscillator. The wireless device may further usethe TRSs for estimating channel characteristics such as delay spread ordoppler frequency. The base station may use a CSI-RS configuration forconfiguring TRS for the wireless device. The TRS may be configured as aresource set comprising multiple periodic NZP CSI-RS resources.

A base station may configure a UE and the UE may transmit soundingreference signals (SRSs) to enable uplink channel sounding/estimation atthe base station. The SRS may support up to four antenna ports and maybe designed with low cubic metric enabling efficient operation of thewireless device amplifier. The SRS may span one or more (e.g., one, twoor four) consecutive OFDM symbols in time domain and may be locatedwithin the last n (e.g., six) symbols of a slot. In the frequencydomain, the SRS may have a structure that is referred to as a combstructure and may be transmitted on every Nth subcarrier. Different SRStransmissions from different wireless devices may have different combstructures and may be multiplexed in frequency domain.

A base station may configure a wireless device with one or more SRSresource sets and an SRS resource set may comprise one or more SRSresources. The SRS resources in an SRS resources set may be configuredfor periodic, semi-persistent or aperiodic transmission. The periodicSRS and the semi-persistent SRS resources may be configured withperiodicity and offset parameters. The Semi-persistent SRS resources ofa configured semi-persistent SRS resource set may be activated ordeactivated by a semi-persistent (SP) SRS Activation/Deactivation MACCE. The set of SRS resources included in an aperiodic SRS resource setmay be activated by a DCI. A value of a field (e.g., an SRS requestfield) in the DCI may indicate activation of resources in an aperiodicSRS resource set from a plurality of SRS resource sets configured forthe wireless device.

An antenna port may be associated with one or more reference signals.The receiver may assume that the one or more reference signals,associated with the antenna port, may be used for estimating channelcorresponding to the antenna port. The reference signals may be used toderive channel state information related to the antenna port. Twoantenna ports may be referred to as quasi co-located if characteristics(e.g., large-scale properties) of the channel over which a symbol isconveyed on one antenna port may be inferred from the channel over whicha symbol is conveyed from another antenna port. For example, a UE mayassume that radio channels corresponding to two different antenna portshave the same large-scale properties if the antenna ports are specifiedas quasi co-located. In some cases, the UE may assume that two antennaports are quasi co-located based on signaling received from the basestation. Spatial quasi-colocation (QCL) between two signals may be, forexample, due to the two signals being transmitted from the same locationand in the same beam. If a receive beam is good for a signal in a groupof signals that are spatially quasi co-located, it may be assumed alsobe good for the other signals in the group of signals.

The CSI-RS in the downlink and the SRS in uplink may serve asquasi-location (QCL) reference for other physical downlink channels andphysical uplink channels, respectively. For example, a downlink physicalchannel (e.g., PDSCH or PDCCH) may be spatially quasi co-located with adownlink reference signal (e.g., CSI-RS or SSB). The wireless device maydetermine a receive beam based on measurement on the downlink referencesignal and may assume that the determined received beam is also good forreception of the physical channels (e.g., PDSCH or PDCCH) that arespatially quasi co-located with the downlink reference signal.Similarly, an uplink physical channel (e.g., PUSCH or PUCCH) may bespatially quasi co-located with an uplink reference signal (e.g., SRS).The base station may determine a receive beam based on measurement onthe uplink reference signal and may assume that the determined receivedbeam is also good for reception of the physical channels (e.g., PUSCH orPUCCH) that are spatially quasi co-located with the uplink referencesignal.

The Demodulation Reference Signals (DM-RSs) enables channel estimationfor coherent demodulation of downlink physical channels (e.g., PDSCH,PDCCH and PBH) and uplink physical channels (e.g., PUSCH and PUCCH). TheDM-RS may be located early in the transmission (e.g., front-loadedDM-RS) and may enable the receiver to obtain the channel estimate earlyand reduce the latency. The time-domain structure of the DM-RS (e.g.,symbols wherein the DM-RS are located in a slot) may be based ondifferent mapping types.

The Phase Tracking Reference Signals (PT-RSs) enables tracking andcompensation of phase variations across the transmission duration. Thephase variations may be, for example, due to oscillator phase noise. Theoscillator phase noise may become more sever in higher frequencies(e.g., mmWave frequency bands). The base station may configure the PT-RSfor uplink and/or downlink. The PT-RS configuration parameters mayindicate frequency and time density of PT-RS, maximum number of ports(e.g., uplink ports), resource element offset, configuration of uplinkPT-RS without transform precoder (e.g., CP-OFDM) or with transformprecoder (e.g., DFT-s-OFDM), etc. The subcarrier number and/or resourceblocks used for PT-RS transmission may be based on the C-RNTI of thewireless device to reduce risk of collisions between PT-RSs of wirelessdevices scheduled on overlapping frequency domain resources.

FIG. 13B shows example time and frequency structure of CSI-RSs and theirassociation with beams in accordance with several of various embodimentsof the present disclosure. A beam of the L beams shown in FIG. 13B maybe associated with a corresponding CSI-RS resource. The base station maytransmit the CSI-RSs using the configured CSI-RS resources and a UE maymeasure the CSI-RSs (e.g., received signal received power (RSRP) of theCSI-RSs) and report the CSI-RS measurements to the base station based ona reporting configuration. For example, the base station may determineone or more transmission configuration indication (TCI) states and mayindicate the one or more TCI states to the UE (e.g., using RRCsignaling, a MAC CE and/or a DCI). Based on the one or more TCI statesindicated to the UE, the UE may determine a downlink receive beam andreceive downlink transmissions using the receive beam. In case of a beamcorrespondence, the UE may determine a spatial domain filter of atransmit beam based on spatial domain filter of a corresponding receivebeam. Otherwise, the UE may perform an uplink beam selection procedureto determine the spatial domain filter of the transmit beam. The UE maytransmit one or more SRSs using the SRS resources configured for the UEand the base station may measure the SRSs and determine/select thetransmit beam for the UE based the SRS measurements. The base stationmay indicate the selected beam to the UE. The CSI-RS resources shown inFIG. 13B may be for one UE. The base station may configure differentCSI-RS resources associated with a given beam for different UEs by usingfrequency division multiplexing.

A base station and a wireless device may perform beam managementprocedures to establish beam pairs (e.g., transmit and receive beams)that jointly provide good connectivity. For example, in the downlinkdirection, the UE may perform measurements for a beam pair and estimatechannel quality for a transmit beam by the base station (or atransmission reception point (TRP) more generally) and the receive beamby the UE. The UE may transmit a report indicating beam pair qualityparameters. The report may comprise one or more parameters indicatingone or more beams (e.g., a beam index, an identifier of reference signalassociated with a beam, etc.), one or more measurement parameters (e.g.,RSRP), a precoding matrix indicator (PMI), a channel quality indicator(CQI), and/or a rank indicator (RI).

FIG. 14A, FIG. 14B and FIG. 14C show example beam management processes(referred to as P1, P2 and P3, respectively) in accordance with severalof various embodiments of the present disclosure. The P1 process shownin FIG. 14A may enable, based on UE measurements, selection of a basestation (or TRP more generally) transmit beam and/or a wireless devicereceive beam. The TRP may perform a beam sweeping procedure where theTRP may sequentially transmit reference signals (e.g., SSB and/orCSI-RS) on a set of beams and the UE may select a beam from the set ofbeams and may report the selected beam to the TRP. The P2 procedure asshown in FIG. 14B may be a beam refinement procedure. The selection ofthe TRP transmit beam and the UE receive beam may be regularlyreevaluated due to movements and/or rotations of the UE or movement ofother objects. In an example, the base station may perform the beamsweeping procedure over a smaller set of beams and the UE may select thebest beam over the smaller set. In an example, the beam shape may benarrower compared to beam selected based on the P1 procedure. Using theP3 procedure as shown in FIG. 14C, the TRP may fix its transmit beam andthe UE may refine its receive beam.

A wireless device may receive one or more messages from a base station.The one or more messages may comprise one or more RRC messages. The oneor more messages may comprise configuration parameters of a plurality ofcells for the wireless device. The plurality of cells may comprise aprimary cell and one or more secondary cells. For example, the pluralityof cells may be provided by a base station and the wireless device maycommunicate with the base station using the plurality of cells. Forexample, the plurality of cells may be provided by multiple base station(e.g., in case of dual and/or multi-connectivity). The wireless devicemay communicate with a first base station, of the multiple basestations, using one or more first cells of the plurality of cells. Thewireless device may communicate with a second base station of themultiple base stations using one or more second cells of the pluralityof cells.

The one or more messages may comprise configuration parameters used forprocesses in physical, MAC, RLC, PCDP, SDAP, and/or RRC layers of thewireless device. For example, the configuration parameters may includevalues of timers used in physical, MAC, RLC, PCDP, SDAP, and/or RRClayers. For example, the configuration parameters may include parametersfor configurating different channels (e.g., physical layer channel,logical channels, RLC channels, etc.) and/or signals (e.g., CSI-RS, SRS,etc.).

Upon starting a timer, the timer may start running until the timer isstopped or until the timer expires. A timer may be restarted if it isrunning. A timer may be started if it is not running (e.g., after thetimer is stopped or after the timer expires). A timer may be configuredwith or may be associated with a value (e.g., an initial value). Thetimer may be started or restarted with the value of the timer. The valueof the timer may indicate a time duration that the timer may be runningupon being started or restarted and until the timer expires. Theduration of a timer may not be updated until the timer is stopped orexpires (e.g., due to BWP switching). This specification may disclose aprocess that includes one or more timers. The one or more timers may beimplemented in multiple ways. For example, a timer may be used by thewireless device and/or base station to determine a time window [t1, t2],wherein the timer is started at time t1 and expires at time t2 and thewireless device and/or the base station may be interested in and/ormonitor the time window [t1, t2], for example to receive a specificsignaling. Other examples of implementation of a timer may be provided.

FIG. 15 shows example components of a wireless device and a base stationthat are in communication via an air interface in accordance withseveral of various embodiments of the present disclosure. The wirelessdevice 1502 may communicate with the base station 1542 over the airinterface 1532. The wireless device 1502 may include a plurality ofantennas. The base station 1542 may include a plurality of antennas. Theplurality of antennas at the wireless device 1502 and/or the basestation 1542 enables different types of multiple antenna techniques suchas beamforming, single-user and/or multi-user MIMO, etc.

The wireless device 1502 and the base station 1542 may have one or moreof a plurality of modules/blocks, for example RF front end (e.g., RFfront end 1530 at the wireless device 1502 and RF front end 1570 at thebase station 1542), Data Processing System (e.g., Data Processing System1524 at the wireless device 1502 and Data Processing System 1564 at thebase station 1542), Memory (e.g., Memory 1512 at the wireless device1502 and Memory 1542 at the base station 1542). Additionally, thewireless device 1502 and the base station 1542 may have othermodules/blocks such as GPS (e.g., GPS 1514 at the wireless device 1502and GPS 1554 at the base station 1542).

An RF front end module/block may include circuitry between antennas anda Data Processing System for proper conversion of signals between thesetwo modules/blocks. An RF front end may include one or more filters(e.g., Filter(s) 1526 at RF front end 1530 or Filter(s) 1566 at the RFfront end 1570), one or more amplifiers (e.g., Amplifier(s) 1528 at theRF front end 1530 and Amplifier(s) 1568 at the RF front end 1570). TheAmplifier(s) may comprise power amplifier(s) for transmission andlow-noise amplifier(s) (LNA(s)) for reception.

The Data Processing System 1524 and the Data Processing System 1564 mayprocess the data to be transmitted or the received signals byimplementing functions at different layers of the protocol stack such asPHY, MAC, RLC, etc. Example PHY layer functions that may be implementedby the Data Processing System 1524 and/or 1564 may include forward errorcorrection, interleaving, rate matching, modulation, precoding, resourcemapping, MIMO processing, etc. Similarly, one or more functions of theMAC layer, RLC layer and/or other layers may be implemented by the DataProcessing System 1524 and/or the Data Processing System 1564. One ormore processes described in the present disclosure may be implemented bythe Data Processing System 1524 and/or the Data Processing System 1564.A Data Processing System may include an RF module (RF module 1516 at theData Processing System 1524 and RF module 1556 at the Data ProcessingSystem 1564) and/or a TX/RX processor (e.g., TX/RX processor 1518 at theData Processing System 1524 and TX/RX processor 1558 at the DataProcessing System 1566) and/or a central processing unit (CPU) (e.g.,CPU 1520 at the Data Processing System 1524 and CPU 1560 at the DataProcessing System 1564) and/or a graphical processing unit (GPU) (e.g.,GPU 1522 at the Data Processing System 1524 and GPU 1562 at the DataProcessing System 1564).

The Memory 1512 may have interfaces with the Data Processing System 1524and the Memory 1552 may have interfaces with Data Processing System1564, respectively. The Memory 1512 or the Memory 1552 may includenon-transitory computer readable mediums (e.g., Storage Medium 1510 atthe Memory 1512 and Storage Medium 1550 at the Memory 1552) that maystore software code or instructions that may be executed by the DataProcessing System 1524 and Data Processing System 1564, respectively, toimplement the processes described in the present disclosure. The Memory1512 or the Memory 1552 may include random-access memory (RAM) (e.g.,RAM 1506 at the Memory 1512 or RAM 1546 at the Memory 1552) or read-onlymemory (ROM) (e.g., ROM 1508 at the Memory 1512 or ROM 1548 at theMemory 1552) to store data and/or software codes.

The Data Processing System 1524 and/or the Data Processing System 1564may be connected to other components such as a GPS module 1514 and a GPSmodule 1554, respectively, wherein the GPS module 1514 and a GPS module1554 may enable delivery of location information of the wireless device1502 to the Data Processing System 1524 and location information of thebase station 1542 to the Data Processing System 1564. One or more otherperipheral components (e.g., Peripheral Component(s) 1504 or PeripheralComponent(s) 1544) may be configured and connected to the dataProcessing System 1524 and data Processing System 1564, respectively.

In example embodiments, a wireless device may be configured withparameters and/or configuration arrangements. For example, theconfiguration of the wireless device with parameters and/orconfiguration arrangements may be based on one or more control messagesthat may be used to configure the wireless device to implement processesand/or actions. The wireless device may be configured with theparameters and/or the configuration arrangements regardless of thewireless device being in operation or not in operation. For example,software, firmware, memory, hardware and/or a combination thereof and/oralike may be configured in a wireless device regardless of the wirelessdevice being in operation or not operation. The configured parametersand/or settings may influence the actions and/or processes performed bythe wireless device when in operation.

In example embodiments, a wireless device may receive one or moremessage comprising configuration parameters. For example, the one ormore messages may comprise radio resource control (RRC) messages. Aparameter of the configuration parameters may be in at least one of theone or more messages. The one or more messages may comprise informationelement (IEs). An information element may be a structural element thatincludes single or multiple fields. The fields in an IE may beindividual contents of the IE. The terms configuration parameter, IE andfield may be used equally in this disclosure. The IEs may be implementedusing a nested structure, wherein an IE may include one or more otherIEs and an IE of the one or more other IEs may include one or moreadditional IEs. With this structure, a parent IE contains all theoffspring IEs as well. For example, a first IE containing a second IE,the second IE containing a third IE, and the third IE containing afourth IE may imply that the first IE contains the third IE and thefourth IE.

In an example, wireless device with infrequent data transmission may bemaintained in an RRC_INACTIVE state. The data transmission inRRC_INACTIVE state may be periodic and/or non-periodic. For small andinfrequent the data packets for UL (e.g., mobile originated (MO)) dataand/or DL (e.g., mobile terminated (MT)) data, resuming RRC connection(e.g., moving to RRC_CONNECTED state) and subsequently releasing the RRCconnection to INACTIVE state may result in unnecessary power consumptionand signaling overhead.

Examples of small and infrequent data traffic may include: smartphoneapplications (e.g., traffic from Instant Messaging services,heart-beat/keep-alive traffic from IM/email clients and other apps, pushnotifications from various applications, etc.); non-smartphoneapplications (e.g., traffic from wearables (periodic positioninginformation, etc.); sensors (e.g., Industrial Wireless Sensor Networkstransmitting temperature, pressure readings periodically or in anevent-triggered manner, etc.); smart meters and smart meter networkssending periodic meter readings, etc.

Signaling overhead from inactive state UEs for small data packets maydegrade network performance and efficiency and may degrade UE batteryperformance. Example embodiments enhance wireless devices processes inINACTIVE state. Example embodiments may enhance the wireless deviceprocesses in INACTIVE state for small data transmission. Exampleembodiments may employ RACH-based processes (e.g., two-step RACH and/orfour-step RACH) or configured/pre-configured grants (e.g., configuredgrants based on a Type 1 configured grant configuration) and/or periodicresources for uplink data transmission during inactive state.

In an example, for mobile originated case, four-step RACH basedtransmission, two-step RACH based transmission andPre-configured/configured grant-based solution may be considered.

In an example, a wireless device in an RRC_INACTIVE state may remain inCM-CONNECTED (connection management connected) and may move within anarea (e.g., the RAN notification area (RNA)) configured by base stationwithout notifying the base station. In RRC_INACTIVE, the last servinggNB node may keep the UE context and the UE-associated NG connectionwith the serving AMF and UPF.

In an example, the last serving gNB may receive DL data from the UPF orDL UE-associated signaling from the AMF (except the UE Context ReleaseCommand message) while the UE is in RRC_INACTIVE. The last serving gNBmay page in the cells corresponding to the RNA and may send XnAP RANPaging to neighbor gNB(s) if the RNA includes cells of neighbor gNB(s).

In an example, upon receiving a UE Context Release Command message whilethe UE is in RRC_INACTIVE, the last serving gNB may page in the cellscorresponding to the RNA and may send XnAP RAN Paging to neighbor gNB(s)if the RNA includes cells of neighbor gNB(s), in order to release UEexplicitly.

In an example, upon receiving an NG RESET message while the UE is inRRC_INACTIVE, the last serving gNB may page involved UEs in the cellscorresponding to the RNA and may send XnAP RAN Paging to neighbor gNB(s)if the RNA includes cells of neighbor gNB(s) in order to explicitlyrelease involved UEs.

In an example, an AMF may provide to the base station node the CoreNetwork Assistance Information to assist the base station decisionwhether the UE may be sent to RRC_INACTIVE. The Core Network AssistanceInformation may include the registration area configured for the UE, thePeriodic Registration Update timer, and the UE Identity Index value, andmay include the UE specific discontinuous reception (DRX), an indicationif the UE is configured with Mobile Initiated Connection Only (MICO)mode by the AMF, and the Expected UE Behavior. The UE registration areamay be taken into account by the base station node when configuring theRNA. The UE specific DRX and UE Identity Index value may be used by thebase station for RAN paging. The Periodic Registration Update timer maybe taken into account by the base station to configure Periodic RNAUpdate timer. The base station may take into account the Expected UEBehavior to assist the UE RRC state transition decision.

In an example, at transition to RRC_INACTIVE, the base station mayconfigure the UE with a periodic RNA Update timer value.

In an example, if the UE accesses a gNB other than the last serving gNB,the receiving gNB may trigger the XnAP Retrieve UE Context procedure toget the UE context from the last serving gNB and may trigger an Xn-UAddress Indication procedure including tunnel information for potentialrecovery of data from the last serving gNB. Upon successful UE contextretrieval, the receiving gNB may perform the slice-aware admissioncontrol in case of receiving slice information and may become theserving gNB and may further trigger the NGAP Path Switch Request andapplicable RRC procedures. After the path switch procedure, the servinggNB may trigger release of the UE context at the last serving gNB bymeans of the XnAP UE Context Release procedure.

In an example, in case the wireless device is not reachable at the lastserving gNB, the gNB may: fail an AMF initiated UE-associated class 1procedure which may allow the signaling of unsuccessful operation in therespective response message; and may trigger the NAS Non DeliveryIndication procedure to report the non-delivery of any NAS PDU receivedfrom the AMF for the UE.

In an example, if the UE accesses a gNB other than the last serving gNBand the receiving gNB does not find a valid UE Context, the receivinggNB may perform establishment of a new RRC connection instead ofresumption of the previous RRC connection. UE context retrieval may failand hence a new RRC connection may need to be established if the servingAMF changes.

In an example, a UE in the RRC_INACTIVE state may be required toinitiate RNA update procedure when the UE moves out of the configuredRNA. When receiving RNA update request from the UE, the receiving gNBmay trigger the XnAP Retrieve UE Context procedure to get the UE contextfrom the last serving gNB and may decide to send the UE back toRRC_INACTIVE state, move the UE into RRC_CONNECTED state, or send the UEto RRC_IDLE. In case of periodic RNA update, if the last serving gNBdecides not to relocate the UE context, the last serving gNB may failthe Retrieve UE Context procedure and may send the UE back toRRC_INACTIVE, or to RRC_IDLE directly by an encapsulated RRCReleasemessage.

In an example, a UE in RRC_INACTIVE may perform cell reselection.

In an example, a UE in the RRC_INACTIVE state may be configured with anRNA by the last serving base station. The RNA may cover a single cell ormultiple cells. In an example, the RNA may be contained within the CNregistration area. In an example, Xn connectivity may be availablewithin the RNA. In an example, a RAN-based notification area update(RNAU) may be periodically sent by the UE and may be sent when the cellreselection procedure of the UE selects a cell that does not belong tothe configured RNA.

In an example, the RNA may be configured as a list of cells: a UE may beprovided an explicit list of cells (one or more) that constitute theRNA. In an example, the RNA may be configured as list of RAN areas. A UEmay be provided (at least one) RAN area ID, where a RAN area may be asubset of a CN Tracking Area or equal to a CN Tracking Area. A RAN areamay be specified by one RAN area ID, which may comprise of a TAC andoptionally a RAN area Code. In an example, a cell may broadcast one ormore RAN area IDs in the system information.

In an example, base station may provide different RNA definitions todifferent UEs but not mix different definitions to the same UE at thesame time. UE may support RNA configuration options indicated above.

An example UE triggered transition from RRC_INACTIVE to RRC_CONNECTED incase of UE context retrieval success is shown in FIG. 16. Exampleactions for this process may be as follows:

The UE may resume from RRC_INACTIVE, providing the I-RNTI, allocated bythe last serving gNB.The gNB, if able to resolve the gNB identity contained in the I-RNTI,may request the last serving gNB to provide UE Context data.The last serving gNB may provide UE context data.The gNB and UE completes the resumption of the RRC connection. User Datamay be sent if the grant allows.If loss of DL user data buffered in the last serving gNB may beprevented, the gNB may provide forwarding addresses.The gNB may perform path switch.The gNB may trigger the release of the UE resources at the last servinggNB.

In an example, after the first action indicated above, when the gNBdecides to reject the Resume Request and keep the UE in RRC_INACTIVEwithout any reconfiguration or when the gNB decides to setup a new RRCconnection, SRB0 (without security) may be used. When the gNB decides toreconfigure the UE (e.g., with a new DRX cycle or RNA) or when the gNBdecides to push the UE to RRC IDLE, SRB1 (with at least integrityprotection) may be used.

An example UE triggered transition from RRC_INACTIVE to RRC_CONNECTED incase of UE context retrieval failure is shown in FIG. 17. Exampleactions for this process may be as follows:

The UE resumes from RRC_INACTIVE, providing the I-RNTI, allocated by thelast serving gNB.The gNB, if able to resolve the gNB identity contained in the I-RNTI,may request the last serving gNB to provide UE Context data.The last serving gNB may not retrieve or verify the UE context data.The last serving gNB may indicate the failure to the gNB.The gNB may perform a fallback to establish a new RRC connection bysending RRCSetup.A new connection may be set up.

An example rejection from the network when the UE attempts to resume aconnection from RRC_INACTIVE is shown in FIG. 18. Example actions forthis process may be as follows: UE may attempt to resume the connectionfrom RRC_INACTIVE.

The gNB may not be able to handle the procedure, for instance due tocongestion.The gNB may send RRCReject (with a wait time) to keep the UE inRRC_INACTIVE.

An example network-triggered transition from RRC_INACTIVE toRRC_CONNECTED is shown in FIG. 19. Example actions for this process maybe as follows:

A RAN paging trigger event may occur (e.g., incoming DL user plane, DLsignaling from 5GC, etc.).RAN paging may be triggered; either only in the cells controlled by thelast serving gNB or also by means of Xn RAN Paging in cells controlledby other gNB s, configured to the UE in the RAN-based Notification Area(RNA).The UE may be paged with the I-RNTI.If the UE has been successfully reached, the UE may attempt to resumefrom RRC_INACTIVE.

An example UE-triggered RNA update procedure involving context retrievalover Xn is shown in FIG. 20. The procedure may be triggered when the UEmoves out of the configured RNA, or periodically. Example actions forthis process may be as follows:

The UE may resume from RRC_INACTIVE, providing the I-RNTI allocated bythe last serving gNB and appropriate cause value, e.g., RAN notificationarea update.The gNB, if able to resolve the gNB identity contained in the I-RNTI,may request the last serving gNB to provide UE Context, providing thecause value received in the first action.The last serving gNB may provide the UE context. Alternatively, the lastserving gNB may decide to move the UE to RRC_IDLE or, if the UE is stillwithin the previously configured RNA, to keep the UE context in the lastserving gNB and to keep the UE in RRC_INACTIVE.The gNB may move the UE to RRC_CONNECTED or may send the UE back toRRC_IDLE (in which case an RRCRelease message may be sent by the gNB),or send the UE back to RRC_INACTIVE.If loss of DL user data buffered in the last serving gNB may beprevented, the gNB may provide forwarding addresses.The gNB performs path switch.The gNB may keep the UE in RRC_INACTIVE state by sending RRCRelease withsuspend indication.The gNB may trigger the release of the UE resources at the last servinggNB.

An example RNA update procedure for the case when the UE is still withinthe configured RNA and the last serving gNB decides not to relocate theUE context and to keep the UE in RRC_INACTIVE is shown in FIG. 21.Example actions for this process may be as follows: The UE may resumefrom RRC_INACTIVE, providing the I-RNTI allocated by the last servinggNB and appropriate cause value, e.g., RAN notification area update.

The gNB, if able to resolve the gNB identity contained in the I-RNTI,may request the last serving gNB to provide UE Context, providing thecause value received in the first action. The last serving gNB may storereceived information to be used in the next resume attempt (e.g., C-RNTIand PCI related to the resumption cell) and may respond to the gNB withthe RETRIEVE UE CONTEXT FAILURE message including an encapsulatedRRCRelease message. The RRCRelease message may include SuspendIndication.The gNB may forward the RRCRelease message to the UE.

An example RNA update procedure for the case when the last serving gNBdecides to move the UE to RRC_IDLE is shown in FIG. 22. Example actionsfor this process may be as follows:

The UE may resume from RRC_INACTIVE, providing the I-RNTI allocated bythe last serving gNB and appropriate cause value, e.g., RAN notificationarea update.The gNB, if able to resolve the gNB identity contained in the I-RNTI,may request the last serving gNB to provide UE Context, providing thecause value received in the first action.Instead of providing the UE context, the last serving gNB may provide anRRCRelease message to move the UE to RRC_IDLE.The last serving gNB may delete the UE context.The gNB may send the RRCRelease which may trigger the UE to move toRRC_IDLE.

In an example, the suspension of the RRC connection may be initiated bythe network. When the RRC connection is suspended, the UE may store theUE Inactive AS context and configuration received from the network andmay transit to RRC_INACTIVE state. If the UE is configured withsecondary cell group (SCG), the UE may release the SCG configurationupon initiating an RRC Connection Resume procedure.

The resumption of a suspended RRC connection may be initiated by upperlayers when the UE needs to transit from RRC_INACTIVE state toRRC_CONNECTED state or by RRC layer to perform an RNA update or by RANpaging from BASE STATION. When the RRC connection is resumed, networkmay configure the UE according to the RRC connection resume procedurebased on the stored UE Inactive AS context and RRC configurationreceived from the network. The RRC connection resume procedure mayre-activate AS security and re-establish SRB(s) and DRB(s).

In an example, in response to a request to resume the RRC connection,the network may resume the suspended RRC connection and may send UE toRRC_CONNECTED, or may reject the request to resume and send UE toRRC_INACTIVE (with a wait timer), or directly re-suspend the RRCconnection and may send UE to RRC_INACTIVE, or may directly release theRRC connection and send UE to RRC_IDLE, or may instruct the UE toinitiate NAS level recovery (in this case the network may send an RRCsetup message).

In an example, purpose of an RRC Connection release procedure may be torelease the RRC connection, which may include the release of theestablished radio bearers and radio resources; or to suspend the RRCconnection only if SRB2 and at least one DRB are setup, which mayinclude the suspension of the established radio bearers.

In an example, the network may initiate the RRC connection releaseprocedure to transit a UE in RRC_CONNECTED to RRC_IDLE; or to transit aUE in RRC_CONNECTED to RRC_INACTIVE only if SRB2 and at least one DRB issetup in RRC_CONNECTED; or to transit a UE in RRC_INACTIVE back toRRC_INACTIVE when the UE tries to resume; or to transit a UE inRRC_INACTIVE to RRC_IDLE when the UE tries to resume. The procedure maybe used to release and redirect a UE to another frequency.

In an example, an RRCRelease message may be used to command the releaseof an RRC connection or the suspension of the RRC connection. AsuspendConfig information element may Indicate configuration for theRRC_INACTIVE state.

In an example, an RRCResume message may be used to resume the suspendedRRC connection.

In an example, an RRCResumeComplete message may be used to confirm thesuccessful completion of an RRC connection resumption.

In an example, an RRCResumeRequest message may be used to request theresumption of a suspended RRC connection or to perform an RNA update. AresumeCause IE in the RRCResumeRequest message may provide the resumecause for the RRC connection resume request as provided by the upperlayers or RRC. The network may not be expected to reject anRRCResumeRequest due to unknown cause value being used by the UE. In anexample, a resumeIdentity IE may indicate a UE identity to facilitate UEcontext retrieval at gNB.

In an example, a RRCResumeRequest1 message may be used to request theresumption of a suspended RRC connection or perform an RNA update. AresumeCause IE may provide the resume cause for the RRCResumeRequest1 asprovided by the upper layers or RRC. A gNB may not be expected to rejectan RRCResumeRequest1 due to unknown cause value being used by the UE. AresumeIdentity IE may indicate a UE identity to facilitate UE contextretrieval at gNB.

In an example, an IE I-RNTI-Value may be used to identify the suspendedUE context of a UE in RRC_INACTIVE. In an example, the IEShortI-RNTI-Value may be used to identify the suspended UE context of aUE in RRC_INACTIVE using fewer bits compared to I-RNTI-Value.

In an example, Semi-Persistent Scheduling (SPS) may be configured by RRCper Serving Cell and per BWP. Activation and deactivation of the DL SPSmay be independent among the Serving Cells.

In an example, for the DL SPS, a DL assignment may be provided by PDCCH,and may be stored or cleared based on L1 signaling indicating SPSactivation or deactivation.

In an example, RRC may configure the following parameters when SPS isconfigured: cs-RNTI: CS-RNTI for activation, deactivation, andretransmission; nrofHARQ-Processes: the number of configured HARQprocesses for SPS; periodicity: periodicity of configured downlinkassignment for SPS.

In an example, when SPS is released by upper layers, the correspondingconfigurations may be released.

In an example, after a downlink assignment is configured for SPS, theMAC entity may consider sequentially that the Nth downlink assignmentoccurs in the slot for which:

(numberOfSlotsPerFrame×SFN+slot number in theframe)=[(numberOfSlotsPerFrame×SFNstart time+slotstarttime)+N×periodicity×numberOfSlotsPerFrame/10] modulo(1024×numberOfSlotsPerFrame)

where SFNstart time and slotstart time are the SFN and slot,respectively, of the first transmission of PDSCH where the configureddownlink assignment was (re-)initialized.

In an example, for a configured grant Type 1, an uplink grant may beprovided by RRC, and may be stored as configured uplink grant.

In an example, for configured grant Type 2, an uplink grant may beprovided by PDCCH, and stored or cleared as configured uplink grantbased on L1 signalling indicating configured uplink grant activation ordeactivation.

In an example, Type 1 and Type 2 configured grants may be configured byRRC per Serving Cell and per BWP. Multiple configurations may be activesimultaneously. For Type 2, activation and deactivation may beindependent among the Serving Cells. For the same Serving Cell, the MACentity may be configured with either Type 1 or Type 2.

In an example, RRC may configure the following parameters when theconfigured grant Type 1 is configured: cs-RNTI: CS-RNTI forretransmission; periodicity: periodicity of the configured grant Type 1;timeDomainOffset: Offset of a resource with respect to SFN=0 in timedomain; timeDomainAllocation: Allocation of configured uplink grant intime domain which may contain startSymbolAndLength; nrofHARQ-Processes:the number of HARQ processes for configured grant.

In an example, RRC may configure the following parameters when theconfigured grant Type 2 is configured: cs-RNTI: CS-RNTI for activation,deactivation, and retransmission; periodicity: periodicity of theconfigured grant Type 2; nrofHARQ-Processes: the number of HARQprocesses for configured grant.

In an example, upon configuration of a configured grant Type 1 for aServing Cell by upper layers, the MAC entity may: store the uplink grantprovided by upper layers as a configured uplink grant for the indicatedServing Cell; initialize or re-initialize the configured uplink grant tostart in the symbol according to timeDomainOffset and S (derived fromSLIV), and to reoccur with periodicity.

In an example, after an uplink grant is configured for a configuredgrant Type 1, the MAC entity may consider that the uplink grant recursassociated with each symbol for which:

[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in theframe×numberOfSymbolsPerSlot)+symbol number in theslot]=(timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity) modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot), for all N>=0.

In an example, after an uplink grant is configured for a configuredgrant Type 2, the MAC entity may consider that the uplink grant recursassociated with each symbol for which:

[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in theframe×numberOfSymbolsPerSlot)+symbol number in the slot]=[(SFNstarttime×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotstarttime×numberOfSymbolsPerSlot+symbolstart time)+N×periodicity] modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot), for all N>=0.

where SFNstart time, slotstart time, and symbolstart time are the SFN,slot, and symbol, respectively, of the first transmission opportunity ofPUSCH where the configured uplink grant was (re-)initialized.

In an example, when a configured uplink grant is released by upperlayers, the corresponding configurations may be released, andcorresponding uplink grants may be cleared.

In an example, HARQ process identifier for a configured grant may bebased on the the equation: HARQ ProcessID=[floor(CURRENT_symbol/periodicity)] modulo nrofHARQ-Processes, whereCURRENT_symbol=(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotnumber in the frame×numberOfSymbolsPerSlot+symbol number in the slot),and numberOfSlotsPerFrame and numberOfSymbolsPerSlot may refer to thenumber of consecutive slots per frame and the number of consecutivesymbols per slot, respectively. In an example, CURRENT_symbol may referto the symbol index of the first transmission occasion of a repetitionbundle that takes place. In an example, a HARQ process may be configuredfor a configured uplink grant if the configured uplink grant isactivated and the associated HARQ process ID is less thannrofHARQ-Processes.

In an example, the IE ConfiguredGrantConfig may be used to configureuplink transmission without dynamic grant according to two possibleschemes. The actual uplink grant may either be configured via RRC(type1) or provided via the PDCCH (addressed to CS-RNTI) (type2).

In an example, the IE SPS-Config may be used to configure downlinksemi-persistent transmission. Downlink SPS may be configured on theSpCell as well as on SCells. In an example, the network may configureSPS-Config for at most one cell in a cell group.

In an example, Paging may enable the network to reach UEs in RRC IDLEand in RRC_INACTIVE state through Paging messages, and to notify UEs inRRC IDLE, RRC_INACTIVE and RRC_CONNECTED state of system informationchange and ETWS/CMAS indications through Short Messages. Both Pagingmessages and Short Messages may be addressed with P-RNTI on PDCCH, butwhile the former is sent on PCCH, the latter may be sent over PDCCHdirectly.

In an example, while in RRC_IDLE, a UE may monitor the paging channelsfor CN-initiated paging; in RRC_INACTIVE the UE may also monitor pagingchannels for RAN-initiated paging. A UE may not monitor paging channelscontinuously. In an example, paging DRX may be defined and the UE inRRC_IDLE or RRC_INACTIVE may monitor paging channels during one PagingOccasion (PO) per DRX cycle. The Paging DRX cycles are configured by thenetwork: for CN-initiated paging, a default cycle may be broadcast insystem information; for CN-initiated paging, a UE specific cycle may beconfigured via NAS signaling; for RAN-initiated paging, a UE-specificcycle may be configured via RRC signaling.

In an example, the POs of a UE for CN-initiated and RAN-initiated pagingmay be based on the same UE ID, resulting in overlapping POs for both.The number of different POs in a DRX cycle may be configurable viasystem information and a network may distribute UEs to those POs basedon their IDs.

In an example, when in RRC_CONNECTED, the UE may monitor the pagingchannels in a PO signaled in system information for SI change indicationand PWS notification. In case of bandwidth adaptation (BA), a UE inRRC_CONNECTED may monitor paging channels on the active BWP with commonsearch space configured.

In an example, for paging optimization for UEs in CM_IDLE: at UE contextrelease, the BASE STATION node may provide the AMF with a list ofrecommended cells and BASE STATION nodes as assistance info forsubsequent paging. The AMF may provide Paging Attempt Informationcomprising a Paging Attempt Count and the Intended Number of PagingAttempts and may include the Next Paging Area Scope. If Paging AttemptInformation is included in the Paging message, a paged BASE STATION nodemay receive the same information during a paging attempt. The PagingAttempt Count may be increased by one at each new paging attempt. TheNext Paging Area Scope, when present, may indicate whether the AMF plansto modify the paging area currently selected at next paging attempt. Ifthe UE has changed its state to CM CONNECTED the Paging Attempt Countmay be reset.

In an example, for paging optimization for UEs in RRC_INACTIVE: at RANPaging, the serving BASE STATION node may provide RAN Paging areainformation. The serving BASE STATION node may provide RAN Pagingattempt information. A paged BASE STATION node may receive the same RANPaging attempt information during a paging attempt with the followingcontent: Paging Attempt Count, the intended number of paging attemptsand the Next Paging Area Scope. The Paging Attempt Count may beincreased by one at each new paging attempt. The Next Paging Area Scope,when present, may indicate whether the serving NG_RAN node plans tomodify the RAN Paging Area currently selected at next paging attempt. Ifthe UE leaves RRC_INACTIVE state, the Paging Attempt Count may be reset.

In an example, the network may initiate the paging procedure bytransmitting the Paging message at the UE's paging occasion. The networkmay address multiple UEs within a Paging message by including onePagingRecord for each UE.

In an example, the PCCH-Message class may be the set of RRC messagesthat may be sent from the Network to the UE on the PCCH logical channel.

In an example, the Paging message may be used for the notification ofone or more UEs.

In an example, the RRCRelease message may be used to command the releaseof an RRC connection or the suspension of the RRC connection. Asuspendconfig IE in the RRCRelease message may indicate configurationfor the RRC_INACTIVE state. The suspendconfig may comprise a pluralityof parameters comprising a full-RNTI, a short-RNTI, a ran-PagingCycle, aran-NotificationAreaInfo and a t380. The ran-PagingCycle may indicate aUE specific cycle for RAN-initiated paging. The ran-NotoficationAreaInfomay indicate information about a RAN notification area (RNA) (e.g., thecell list). The t380 timer may indicate a timer that triggers theperiodic RNAU procedure in UE.

In an example, an IE SearchSpace may define how/where to search forPDCCH candidates. A search space may be associated with aControlResourceSet. In an example, a parameter common may indicate thata search space is common search space (CSS) and may indicate DCI formatsto monitor. A parameter controlResourceSetId may indicate the CORESETapplicable for the SearchSpace. A parameter duration may indicate anumber of consecutive slots that a SearchSpace may last in an occasion,e.g., upon a period as given in the periodicityAndOffset. If the fieldis absent, the wireless device may apply the value 1 slot, except forDCI format 2_0. The wireless device may ignore this field for DCI format2_0. The maximum valid duration may be periodicity-1 (periodicity asgiven in the monitoringSlotPeriodicityAndOffset). The parametermonitoringSlotPeriodicityAndOffset may indicate slots for PDCCHMonitoring configured as periodicity and offset. The parametermonitoringSymbolsWithinSlot may indicate the first symbol(s) for PDCCHmonitoring in the slots configured for PDCCH monitoring. The mostsignificant (left) bit may represent the first OFDM in a slot, and thesecond most significant (left) bit represents the second OFDM symbol ina slot and so on. The bit(s) set to one may identify the first OFDMsymbol(s) of the control resource set within a slot. If the cyclicprefix of the BWP is set to extended CP, the last two bits within thebit string may be ignored by the wireless device. The parameternrofCandidates-SFI may indicate the number of PDCCH candidatesspecifically for format 2-0 for the configured aggregation level. Theparameter searchSpaceId may identity the search space. SearchSpaceId=0may identify a searchSpaceZero configured via PBCH (MIB) orServingCellConfigCommon and may not be used in the SearchSpace IE. ThesearchSpaceId may be unique among the BWPs of a Serving Cell. In case ofcross carrier scheduling, search spaces with the same searchSpaceId inscheduled cell and scheduling cell may be linked to each other. Thewireless device may apply the search space for the scheduled cell if theDL BWPs in which the linked search spaces are configured in schedulingcell and scheduled cell are both active. The parameter searchSpaceTypemay indicate whether this is a common search space (present) or a UEspecific search space as well as DCI formats to monitor for. Theparameter ue-Specific may configure this search space as UE specificsearch space (USS). The UE may monitor the DCI format with CRC scrambledby C-RNTI, CS-RNTI (if configured), and SP-CSI-RNTI (if configured).

In an example, an IE SearchSpaceId may be used to identify SearchSpaces. The ID space may be used across the BWPs of a Serving Cell. Thesearch space with the SearchSpaceId=0 may identify the search spaceconfigured via PBCH (MIB) and in ServingCellConfigCommon(searchSpaceZero).

In an example, an IE SearchSpaceZero may be used to configureSearchSpace#0 of the initial BWP. The IE PDCCH-Config may be used toconfigure UE specific PDCCH parameters such as control resource sets(CORESET), search spaces and additional parameters for acquiring thePDCCH. In an example, a parameter controlResourceSetToAddModList mayindicate a list of UE specifically configured Control Resource Sets(CORESETs) to be used by the wireless device. In an example, an IEPDCCH-ConfigCommon may be used to configure cell specific PDCCHparameters provided in SIB as well as in dedicated signaling. In anexample, an IE ControlResourceSet may be used to configure atime/frequency control resource set (CORESET) in which to search fordownlink control information. In an example, a ControlResourceSetId IEmay indicate a short identity, used to identify a control resource setwithin a serving cell. The IE ControlResourceSetZero may be used toconfigure CORESET#0 of the initial BWP.

In an example, in RRC_CONNECTED, a gNB may be responsible formaintaining the timing advance to keep the L1 synchronized. Servingcells having UL to which the same timing advance applies and using thesame timing reference cell may be grouped in a TAG. A TAG may contain atleast one serving cell with configured uplink, and the mapping of aserving cell to a TAG may be configured by RRC. For the primary TAG theUE may use the PCell as timing reference. In a secondary TAG, the UE mayuse any of the activated SCells of the TAG as a timing reference celland may not change it unless necessary. Timing advance updates may besignaled by the gNB to the UE via MAC CE commands. Such commands mayrestart a TAG-specific timer which may indicate whether the L1 can besynchronized or not: when the timer is running, the L1 is consideredsynchronized, otherwise, the L1 is considered non-synchronized (in whichcase uplink transmission may only take place on PRACH).

In an example, RRC may configure the following parameters for themaintenance of UL time alignment: timeAlignmentTimer (per TAG) which maycontrol how long the MAC entity may consider the Serving Cells belongingto the associated TAG to be uplink time aligned.

In an example, when a Timing Advance Command MAC CE is received, and ifan NTA has been maintained with the indicated TAG: The MAC entity mayapply the Timing Advance Command for the indicated TAG and may start orrestart the timeAlignmentTimer associated with the indicated TAG.

In an example, when a Timing Advance Command is received in a RandomAccess Response message for a Serving Cell belonging to a TAG: if theRandom Access Preamble was not selected by the MAC entity among thecontention-based Random Access Preamble: the MAC entity may apply theTiming Advance Command for this TAG; and may start or restart thetimeAlignmentTimer associated with this TAG.

In an example, when a Timing Advance Command is received in a RandomAccess Response message for a Serving Cell belonging to a TAG: if thetimeAlignmentTimer associated with this TAG is not running: the MACentity may apply the Timing Advance Command for this TAG; start thetimeAlignmentTimer associated with this TAG; and may stoptimeAlignmentTimer associated with this TAG when the ContentionResolution is considered not successful or when the ContentionResolution is considered successful for SI request, after transmittingHARQ feedback for MAC PDU including UE Contention Resolution IdentityMAC CE.

In an example, when a Timing Advance Command is received in a RandomAccess Response message for a Serving Cell belonging to a TAG: if thetimeAlignmentTimer associated with this TAG is running: the wirelessdevice may ignore the received Timing Advance Command.

In an example, when a timeAlignmentTimer expires: if thetimeAlignmentTimer is associated with the PTAG: the wireless device mayflush HARQ buffers for Serving Cells; notify RRC to release PUCCH forServing Cells, if configured; notify RRC to release SRS for ServingCells, if configured; clear configured downlink assignments andconfigured uplink grants; clear PUSCH resource for semi-persistent CSIreporting; consider running timeAlignmentTimers as expired; maintain NTAof all TAGs.

In an example, when a timeAlignmentTimer expires: if thetimeAlignmentTimer is associated with an STAG, then for all ServingCells belonging to this TAG: the wireless device may flush HARQ buffers;notify RRC to release PUCCH, if configured; notify RRC to release SRS,if configured; clear configured downlink assignments and configureduplink grants; clear PUSCH resource for semi-persistent CSI reporting;and maintain NTA of this TAG.

In an example, when the MAC entity stops uplink transmissions for anSCell due to the fact that the maximum uplink transmission timingdifference between TAGs of the MAC entity or the maximum uplinktransmission timing difference between TAGs of any MAC entity of the UEis exceeded, the MAC entity may consider the timeAlignmentTimerassociated with the SCell as expired.

In an example, the MAC entity may not perform an uplink transmission ona Serving Cell except the Random Access Preamble transmission when thetimeAlignmentTimer associated with the TAG to which this Serving Cellbelongs is not running. Furthermore, when the timeAlignmentTimerassociated with the PTAG is not running, the MAC entity may not performan uplink transmission on a Serving Cell except the Random AccessPreamble transmission on the SpCell.

In an example, a Timing Advance Command MAC CE may be identified by MACsubheader with a corresponding LCID. The Timing Advance Command MAC CEmay have a fixed size and may comprise of an octet comprising a TAG IDfield and a Timing Advance Command field. The TAG Identity (TAG ID) mayindicate the TAG Identity of the addressed TAG. The TAG containing theSpCell may have a TAG Identity 0. The length of the TAG ID field may be2 bits. The Timing Advance Command field may indicate the index value TA(0, 1, 2 . . . 63) used to control the amount of timing adjustment thatMAC entity has to apply. The length of the Timing Advance Command fieldmay be 6 bits.

In an example, a Logical Channel Prioritization (LCP) procedure may beapplied when a new transmission is performed. The RRC may control thescheduling of uplink data by signaling for each logical channel per MACentity: priority where an increasing priority value indicates a lowerpriority level; prioritisedBitRate which may set the Prioritized BitRate (PBR); bucketSizeDuration which may set the Bucket Size Duration(BSD).

In an example, RRC may additionally control the LCP procedure byconfiguring mapping restrictions for each logical channel:allowedSCS-List which may set the allowed Subcarrier Spacing(s) fortransmission; maxPUSCH-Duration which may set the maximum PUSCH durationallowed for transmission; configuredGrantTypelAllowed which may setwhether a configured grant Type 1 may be used for transmission; andallowedServingCells which may set the allowed cell(s) for transmission.

In an example, the following UE variable may be used for the Logicalchannel prioritization procedure: Bj which may be maintained for eachlogical channel j. The MAC entity may initialize Bj of the logicalchannel to zero when the logical channel is established.

In an example, for a logical channel j, the MAC entity may: increment Bjby the product PBR×T before every instance of the LCP procedure, where Tis the time elapsed since Bj was last incremented; if the value of Bj isgreater than the bucket size (e.g., PBR×BSD): the MAC entity may set Bjto the bucket size.

In an example, the MAC entity, when a new transmission is performed, mayselect the logical channels for each UL grant that satisfy the followingconditions: the set of allowed Subcarrier Spacing index values inallowedSCS-List, if configured, includes the Subcarrier Spacing indexassociated to the UL grant; and maxPUSCH-Duration, if configured, islarger than or equal to the PUSCH transmission duration associated tothe UL grant; and configuredGrantTypelAllowed, if configured, is set totrue in case the UL grant is a Configured Grant Type 1; andallowedServingCells, if configured, includes the Cell informationassociated to the UL grant.

In an example, the Subcarrier Spacing index, PUSCH transmission durationand Cell information may be included in Uplink transmission informationreceived from lower layers for the corresponding scheduled uplinktransmission.

In an example, when a new transmission is performed, the MAC entity mayallocate resources to the logical channels as follows: logical channelsselected for the UL grant with Bj>0 may be allocated resources in adecreasing priority order. If the PBR of a logical channel is set toinfinity, the MAC entity may allocate resources for the data that isavailable for transmission on the logical channel before meeting the PBRof the lower priority logical channel(s); decrement Bj by the total sizeof MAC SDUs served to logical channel j; if any resources remain, thelogical channels selected are served in a strict decreasing priorityorder (regardless of the value of Bj) until either the data for thatlogical channel or the UL grant is exhausted, whichever comes first.Logical channels configured with equal priority may be served equally.

In an example, if the MAC entity is requested to simultaneously transmitmultiple MAC PDUs, or if the MAC entity receives the multiple UL grantswithin one or more coinciding PDCCH occasions (e.g., on differentServing Cells), it may be up to UE implementation in which order thegrants are processed.

In an example, logical channels may be prioritized in accordance with anorder. An example priority (e.g., when the UE is in RRC connected state)is shown below (highest priority listed first):

C-RNTI MAC CE or data from UL-CCCH; Configured Grant Confirmation MACCE;MAC CE for BSR, with exception of BSR included for padding;

Single Entry PHR MAC CE or Multiple Entry PHR MAC CE;

data from any Logical Channel, except data from UL-CCCH;MAC CE for Recommended bit rate query;MAC CE for BSR included for padding.

In an example, the MAC entity may multiplex MAC CEs and MAC SDUs in aMAC PDU according to logical channel prioritization rules.

In an example, an IE LogicalChannelConfig may be used to configure thelogical channel parameters.

In an example, an IE LogicalChannelIdentity may be used to identify onelogical channel (LogicalChannelConfig) and the corresponding RLC bearer(RLC-BearerConfig).

In an example in case of transparent MAC, a MAC PDU may comprise solelyof a MAC SDU whose size is aligned to a TB. This MAC PDU may be used fortransmissions on PCH, BCH, and DL-SCH including BCCH.

In an example, a UE may be configured with one or more SoundingReference Signal (SRS) resource sets as configured by the higher layerparameter SRS-ResourceSet. For an SRS resource set, a UE may beconfigured with K≥1SRS resources (e.g., higher layer parameterSRS-Resource), where the maximum value of K may be indicated by UEcapability. The SRS resource set applicability may be configured by thehigher layer parameter usage in SRS-ResourceSet. When the higher layerparameter usage is set to ‘beamManagement’, one SRS resource in each ofmultiple SRS sets may be transmitted at a given time instant, but theSRS resources in different SRS resource sets with the same time domainbehavior in the same BWP may be transmitted simultaneously.

In an example, for aperiodic SRS at least one state of the DCI field maybe used to select at least one out of the configured SRS resourceset(s).

In an example, SRS parameters may be semi-statically configurable byhigher layer parameter (e.g., SRS-Resource). srs-ResourceId maydetermines SRS resource configuration identity. Number of SRS ports maybe defined by the higher layer parameter nrofSRS-Ports. Time domainbehavior of SRS resource configuration may be indicated by the higherlayer parameter resourceType, and may be periodic, semi-persistent,aperiodic SRS transmission. Slot level periodicity and slot level offsetmay be defined by the higher layer parameters periodicityAndOffset-p orperiodicityAndOffset-sp for an SRS resource of type periodic orsemi-persistent. The UE may not be expected to be configured with SRSresources in the same SRS resource set SRS-ResourceSet with differentslot level periodicities. For an SRS-ResourceSet configured with higherlayer parameter resourceType set to ‘aperiodic’, a slot level offset maybe defined by the higher layer parameter slotOffset. Number of OFDMsymbols in the SRS resource, starting OFDM symbol of the SRS resourcewithin a slot including repetition factor R may be defined by the higherlayer parameter resourceMapping. SRS bandwidth B_(SRS) and C_(SRS), maybe defined by the higher layer parameter freqHopping. Frequency hoppingbandwidth, b_(hop), may be defined by the higher layer parameterfreqHopping. Frequency domain position and configurable shift may bedefined by the higher layer parameters freqDomainPosition andfreqDomainShift, respectively. Cyclic shift may be defined by the higherlayer parameter cyclicShift-n2 or cyclicShift-n4 for transmission combvalue 2 and 4, respectively. Transmission comb value a may be defined bythe higher layer parameter transmissionComb. Transmission comb offsetmay be defined by the higher layer parameter combOffset-n2 orcombOffset-n4 for transmission comb value 2 or 4, respectively. SRSsequence ID may be defined by the higher layer parameter sequenceId.

In an example, the configuration of the spatial relation between areference RS and the target SRS, where the higher layer parameterspatialRelationInfo, if configured, may contain the ID of the referenceRS. The reference RS may be an SS/PBCH block, CSI-RS configured onserving cell indicated by higher layer parameter servingCellId ifpresent, same serving cell as the target SRS otherwise, or an SRSconfigured on uplink BWP indicated by the higher layer parameteruplinkBWP, and serving cell indicated by the higher layer parameterservingCellId if present, same serving cell as the target SRS otherwise.

In an example, the UE may be configured by the higher layer parameterresourceMapping in SRS-Resource with an SRS resource occupyingN_(s)ϵ{1,2,4} adjacent symbols within the last 6 symbols of the slot,where antenna ports of the SRS resources may be mapped to each symbol ofthe resource.

In an example, when PUSCH and SRS are transmitted in the same slot, theUE may be configured to transmit SRS after the transmission of the PUSCHand the corresponding DM-RS.

In an example, for a UE configured with one or more SRS resourceconfiguration(s), and when the higher layer parameter resourceType inSRS-Resource is set to ‘periodic’: if the UE is configured with thehigher layer parameter spatialRelationInfo containing the ID of areference ‘ssb-Index’, the UE may transmit the target SRS resource withthe same spatial domain transmission filter used for the reception ofthe reference SS/PBCH block, if the higher layer parameterspatialRelationInfo contains the ID of a reference ‘csi-RS-Index’, theUE shall transmit the target SRS resource with the same spatial domaintransmission filter used for the reception of the reference periodicCSI-RS or of the reference semi-persistent CSI-RS, if the higher layerparameter spatialRelationInfo containing the ID of a reference ‘srs’,the UE shall transmit the target SRS resource with the same spatialdomain transmission filter used for the transmission of the referenceperiodic SRS.

In an example, RRC_INACTIVE state may be used to reduce networksignaling load and to reduce latency involved in transitioning toRRC_CONNECTED state. In RRC_INACTIVE state, the AS context may be storedby both UE and gNB and the state transition from inactive state toconnected state may be faster and the core network connection may bemaintained (e.g., UE may remain in CM-CONNECTED). In an example, networkmay reach UEs in RRC_INACTIVE state through Paging messages, and maynotify UEs in RRC_INACTIVE, change of system information and ETWS/CMASindications through Short Messages. The Paging messages and/or ShortMessages may be addressed with P-RNTI on PDCCH. The paging messages maybe sent on PCCH and Short Messages may be sent over PDCCH.

In an example, the UE may monitor a Paging channel for CN paging using5G-S-TMSI and RAN paging using full I-RNTI (Inactive RNTI). The I-RNTImay be used to identify the suspended UE context of a UE in RRC_INACTIVEstate. The network may assign I-RNTI to the UE when moving fromRRC_CONNECTED to RRC_INACTIVE state in RRC Release message withinSuspendConfig.

In an RRC_INACTIVE state, a wireless device may transmit data usingrandom access processes and/or using pre-configured/configuredresources. The existing uplink transmission processes for RRC_INACTIVEstate may lead to inefficient uplink transmissions for example due tolack of uplink synchronization and degraded network performance. Thereis a need to enhance the existing processes for uplink transmissionduring the RRC_INACTIVE state. Example embodiments enhance the wirelessdevice and network processes during an RRC_INACTIVE state.

In an example as shown in FIG. 23, a wireless device may receive, from abase station, an RRC release message. The RRC release message mayindicate transitioning of a wireless device from an RRC_CONNECTED stateto an RRC_INACTIVE state. The RRC release message may comprise a suspendconfig information element indicating transitioning from theRRC_CONNECTED state to the RRC_INACTIVE state and/or suspending an RRCconnection with the wireless device. For example, the suspend configinformation element may comprise configuration parameters (e.g., one ormore wireless device identifiers/RNTIs, parameters for one or moreprocesses during the RRC_INACTIVE state) for the wireless deviceoperation in the RRC_INACTIVE state.

The wireless device may be in an RRC_CONNECTED state when receiving theRRC release message. The wireless device may have a running timealignment timer when receiving the RRC release message. For example, aprimary timing advance group (TAG) of the wireless device may have anassociated time alignment timer that may be running when receiving theRRC release message. In an example embodiment, the wireless device maystart a timer based on the receiving the RRC release message. Thewireless device may start the timer based on the receiving the RRCrelease message and/or based on the transitioning from the RRC_CONNECTEDstate to the RRC_INACTIVE state and/or based on the suspending the RRCconnection. The timer may be used by the wireless device to determinewhether the wireless device is uplink time aligned or not. In anexample, the timer may be an RRC timer and/or may be started/maintainedby the RRC layer. In an example, the timer may be a MAC timer and/or maybe started/maintained by the MAC later. In an example, the timer may bea time alignment timer. In an example, the wireless device may start thetimer based on the RRC release message (e.g., the suspend configinformation element in the RRC release message) comprising a timealignment timer value and/or a timing advance value for the wirelessdevice during the RRC_INACTIVE state.

The wireless device may start the timer (e.g., time alignment timer) ata first timing. In an example, the first timing may be based on areference timing and/or a timing offset. In an example, the first timingmay be a timing offset to a reference timing. For example, theprocessing time of the RRC release message by the wireless device maynot be deterministic and the wireless device may start the timer (e.g.,time alignment timer) at the first timing wherein the first timing isdetermined by the wireless device and the base station as the timingoffset to the reference timing. The wireless device and the base stationmay start the timer (e.g., time alignment timer) at the first timing.For example, the reference timing may be a reference system frame number(e.g., system frame number zero). For example, the reference timing maybe a first slot/subframe of a system frame number (e.g., system framenumber zero). The timing offset may be a first number of a time unit.The time unit may be a symbol (e.g., OFDM) symbol duration or a slotduration. For example, the timing offset may be a first number of symboldurations or a first number of slot durations. The timing offset and/orthe number of the time unit may be pre-configured or may beconfigurable. For example, the configuration parameters may indicate thetiming offset and/or the number of the time unit. For example, the RRCrelease message may comprise a parameter indicating the timing offsetvalue and/or the number of the time unit. For example, the suspendconfig IE in the RRC release message may comprise a parameter indicatingthe timing offset value and/or the number of the time unit.

The wireless device, during the RRC_INACTIVE state, may determine thatits uplink transmissions are time aligned while the timer (e.g., thetime alignment timer) is running. For example, the RRC release message(e.g., the suspend config IE in the RRC release message) maycomprise/indicate the timer (e.g., time alignment timer) value and/orthe timing advance value and the wireless device may start the timer(e.g., the time alignment timer) with the timer value indicated by theRRC release message based on the receiving the RRC release message. Oneor more uplink transmissions in the RRC_INACTIVE state may be based onthe timing advance value (indicated by the RRC release message) whilethe timer is running.

In an example as shown in FIG. 24, a wireless device may receiveconfiguration parameters of one or more cells. The one or more cells maycomprise a first cell. In an example, the first cell may be a primarycell. In an example, the one or more cells may be grouped into a timingadvance group (e.g., a primary timing advance group (PTAG)). Thewireless device may receive an RRC release message indicatingtransitioning from an RRC_CONNECTED state to an RRC_INACTIVE stateand/or suspending an RRC connection. The wireless device may have atiming advance for uplink transmissions via the one or more cells beforereceiving the RRC release message and/or before transitioning from theRRC_CONNECTED state to the RRC_INACTIVE state and/or before suspendingthe RRC connection. For example, the timing advance associated with theone or more cells, when receiving the RRC release message may be TA1. Atime alignment timer associated with the one or more cells may berunning when receiving the RRC release message. The wireless device maydetermine the timing advance value that is associated with the one ormore cells before receiving the RRC release message (e.g., beforetransitioning from the RRC CONNECTED state to the RRC_INACTIVE stateand/or before suspending the RRC connection) and while the wirelessdevice is in the RRC_CONNECTED state (e.g., TA1 in FIG. 24). In anexample embodiment, the wireless device may transmit one or more uplinkpackets during the RRC_INACTIVE state and using the determined timingadvance value. In an example, the wireless device may transmit the oneor more uplink packets during the RRC_INACTIVE state and using thetiming advance value while a timer (e.g., a time alignment timer) isrunning. In an example, the timer may be a MAC layer timer (e.g., a timealignment timer) and may be started and/or maintained by the MAC layer.In an example, the timer may be an RRC layer timer and may be startedand/or maintained by the RRC layer.

In an example, the wireless device may start a timer with a timer valuebased on the receiving the RRC release message and/or based on thetransitioning from the RRC_CONNECTED state to the RRC_INACTIVE stateand/or based on the suspending the RRC connection. The wireless devicemay receive configuration parameters comprising/indicating the timervalue. For example, the RRC release message and/or the suspend config IEin the RRC release message may comprise the configuration parameterscomprising/indicating the timer value.

In an example as shown in FIG. 25, a wireless device in an RRC_CONNECTEDstate may receive an RRC release message. The RRC release message mayindicate transitioning of the wireless device from the RRC_CONNECTEDstate to an RRC_INACTIVE state and/or suspending an RRC connection forthe wireless device. The RRC release message may comprise a suspendconfig information element that indicates the transitioning of thewireless device from the RRC_CONNECTED state to the RRC_INACTIVE stateand/or the suspending the RRC connection for the wireless device. In anexample embodiment, the suspend config information element may compriseparameters for the wireless device operation during the RRC_INACTIVEstate, for example one or more parameters for determining uplink timingfor uplink transmissions during the RRC_NACTIVE state. The wirelessdevice may determine uplink timing based on the one or more parameters.The wireless device may transmit uplink packets based on the determineduplink timing.

In an example, the one or more parameters, indicated by the RRC releasemessage and/or the suspend config IE and used for determining the uplinktiming during the RRC_INACTIVE state, may comprise a timing advancevalue. One or more uplink transmissions during the RRC_INACTIVE statemay be based on the timing advance value. For example, the one or moreuplink transmissions during the RRC_INACTIVE state may be based on thetiming advance value and based on a timer (e.g., a time alignment timer)running.

In an example, the one or more parameters, indicated by the RRC releasemessage and/or the suspend config IE and used for determining the uplinktiming during the RRC_INACTIVE state, may comprise a time alignmenttimer value for a time alignment timer. The wireless device may transmitrandom access preambles during the RRC_INACTIVE state based on the timealignment timer.

In an example, the wireless device may start a time alignment timer withthe time alignment timer value indicated by the suspend config IE basedon the receiving the RRC release message and/or based on thetransitioning from the RRC_CONNECTED state to the RRC_INACTIVE stateand/or based on the suspending the RRC connection for the wirelessdevice. The wireless device may start the time alignment timer at afirst timing. The first timing may be based on a reference timing and/ora timing offset. For example, the first timing may be a timing offset toa reference timing. For example, the reference timing may be a referencesystem frame number (e.g., system frame number zero) and/or a firstsubframe/slot in a reference system frame number. The timing offset maybe in terms of a first number of time unit. The time unit may be symbolduration or slot. In an example, the RRC release message and/or thesuspend config IE of the RRC release message may indicate the timingoffset and/or the first number and/or the time unit (e.g., symbol, slot,etc.).

In an example, as shown in FIG. 26 and FIG. 27, a wireless device maystart a random access process in an RRC_INACTIVE state for obtaining atiming advance value. In an example, the wireless device may start therandom access process and/or transmit a random access preamble based onan expiry of a time alignment timer. In an example, the wireless devicemay transmit the random access preamble based on a periodicity. In anexample, the wireless device may receive an RRC release messageindicating transitioning of the wireless device form an RRC_CONNECTEDstate to the RRC_INACTIVE state and the RRC release message and/or asuspend config IE of the RRC release message may comprise one or moreparameters indicating a time alignment timer value of the time alignmenttimer and/or the periodicity parameter. In an example, the timealignment timer value and/or the periodicity parameter may be indicatedvia broadcast system information (e.g., MIB or a SIB). In an example,the wireless device may receive paging information, via a pagingchannel, indicating the time alignment timer value and/or theperiodicity parameter.

For example, as shown in FIG. 26, the random access process may be afour-step random access process and the wireless device may receive arandom access response comprising timing advance value and an plinkgrant. The wireless device may transmit an RRC resume request based onand via the resources indicated by the uplink grant. The RRC resumerequest message may comprise a cause IE. In an example embodiment, avalue of the cause IE may indicate that a cause for the RRC resumerequest message is a timing advance request. The value of the cause IEmay indicate that the cause for the RRC resume request message is not aresumption of the RRC connection. The wireless device may transmituplink data based on the timing advance value indicated by the randomaccess response. The wireless device may transmit the uplink data basedon pre-configured and/or configured resources (e.g., configured grantresources, e.g., Type 1 configured grant resources).

For example, as shown in FIG. 27, the wireless device may transmit anRRC resume request message during a two-step random access process(e.g., via Msg A in a two-step random access process). The RRC resumerequest message may comprise a cause IE. The cause information elementin the RRC resume request message may indicate that a cause for the RRCresume request message is a timing advance request. In an exampleembodiment, the value of the cause IE may indicate that the cause forthe RRC resume request message is not a resumption of the RRCconnection. The wireless device may receive a message (e.g., Msg B)comprising a timing advance value. The wireless device may transmituplink data based on the timing advance value indicated by the message(e.g., Msg B). The wireless device may transmit the uplink data based onpre-configured and/or configured resources (e.g., configured grantresources, e.g., Type 1 configured grant resources). For example,

In an example embodiment as shown in FIG. 28, the wireless device in anRRC_INACTIVE state may transmit a random access preamble. The randomaccess preamble may indicate that the wireless device is requesting atiming advance without a request for resumption of the RRC connection.In an example, the wireless device may receive configuration parametersindicating that one or more random access preambles, comprising therandom access preamble, is for requesting a timing advance without arequest for resumption of the RRC connection (e.g., without a requestfor transitioning to an RRC_CONNECTED state).

The wireless device may transmit the random access preamble as part of atwo-step random access process or a four-step random access process. Forexample, the wireless device may transmit the random access preamblebased on an expiry of a time alignment timer and/or based on aperiodicity parameter (e.g., transmitting random access preamblesperiodically with a period determined based on the periodicityparameter). The wireless device may receive configuration parametersindicating a time alignment timer value for the time alignment timerand/or the periodicity parameter. For example, the wireless device mayreceive the configuration parameters in the RRC release message (e.g.,in a suspend config IE of the RRC release message). For example, thewireless device may receive the time alignment timer value for the timealignment timer and/or the periodicity parameter via broadcast systeminformation (e.g., MIB or a SIB, e.g., SIB1). For example, the wirelessdevice may receive paging information, via a paging channel, indicatingthe time alignment timer value and/or the periodicity parameter.

In response to the transmission of the random access preamble, thewireless device may receive a timing advance value. For example, thewireless device may receive the timing advance in a random accessresponse of a four-step random access process or a Msg B in a two-steprandom access response. In an example, for a four-step random accessprocess, the random access response may further comprise an uplinkgrant. The size of the uplink grant may be based on the random accesspreamble. For example, based on the random access preamble indicatingthat the wireless device is requesting timing advance without resumptionof the RRC connection and/or transitioning to the RRC_CONNECTED state,the size of the uplink grant may be smaller than the case that therandom access preamble indicates that the wireless device requestsresumption of the RRC connection.

The wireless device may transmit one or more packets, while in theRRC_INACTIVE state, based on the timing advance value. The wirelessdevice may transmit the one or more packets via pre-configured resourcesor configured grant resources (e.g., configured grant, e.g., configuredgrant Type 1 resources).

In an example embodiment, a wireless device in an RRC_INACTIVE state maytransmit a random access preamble. The random access preamble mayindicate whether the wireless device is requesting a resumption of anRRC connection and/or requesting an uplink grant for transmission ofUL-CCCH (e.g., for transmission of RRC resume request) or whether thewireless device is not requesting resumption of the RRC connectionand/or requesting an uplink grant for transmission of data withoutUL-CCCH. For example, the wireless device may receive configurationparameters indicating one or more first random access preambles forrequesting an RRC resumption and/or for requesting uplink grant fortransmission of UL-CCCH and one or more second random access preamblesfor requesting uplink grant for transmission of data without UL-CCCH. Inresponse to the transmission of the random access preamble, the wirelessdevice may receive uplink grant, wherein the uplink grant (e.g., a sizeof the uplink grant) may be based on the transmitted random accesspreamble. The wireless device may transmit an uplink packet based on theuplink grant.

In an example embodiment, a wireless device in an RRC_INACTIVE state maytransmit a random access preamble. The random access preamble mayindicate that the wireless device is requesting an uplink grant fortransmitting UL-CCCH (e.g., for transmission of an RRC resume requestmessage). For example, the wireless device may receive configurationparameters indicating one or more first random access preambles,comprising the random access preamble, for requesting an RRC resumptionand/or for requesting uplink grant for transmission of UL-CCCH. Thewireless device may receive, in response to the transmission of therandom access preamble, an uplink grant. Based on the random accesspreamble indicating a request for an uplink grant for transmission ofUL-CCCH, the uplink grant may be useful for transmission of UL-CCCHand/or an RRC resume request message. The wireless device may transmit apacket, comprising data from the UL-CCCH, based on the uplink grant andvia the resources indicated by the uplink grant.

In an example embodiment as shown in FIG. 29, a wireless device may bein an RRC_INACTIVE state. The wireless device may receive a plurality oftiming advance values via a control channel (e.g., PDCCH). In anexample, the wireless device may receive downlink control informationcomprising/indicating the plurality of timing advance values. In anexample, the plurality of timing advance values may be for a pluralityof wireless devices. The wireless device may receive the downlinkcontrol information via the downlink control channel. In an example, thedownlink control information may be a common/group common downlinkcontrol information. The wireless device may receive the downlinkcontrol information via a common search space. The downlink controlinformation comprising the plurality of timing advance values may beassociated with a wireless device identifier/RNTI. For example, a CRC ofthe downlink control information comprising the plurality of timingadvance values may be scrambled with the wireless deviceidentifier/RNTI. The wireless device may receive configurationparameters comprising the wireless device identifier/RNTI. For example,the wireless device may receive an RRC release message indicatingtransitioning of the wireless device from RRC_CONNECTED to RRC_INACTIVEwherein the RRC release message or a suspend config IE of the RRCrelease message may indicate the wireless device identifier/RNTI. Thesuspend config IE may comprise configuration parameters for wirelessdevice operation during the RRC_INACTIVE state.

The wireless device may determine a first timing advance value in theplurality of timing advance values. In an example, the wireless devicemay determine the first timing advance value, in the plurality of timingadvance values, based on an index/identifier associated with thewireless device. For example, each timing advance value, in theplurality of timing advance values, may correspond to an index and/oridentifier and the wireless device may determine the first timingadvance value based on the index/identifier associated with the wirelessdevice. The wireless device may receive configuration parameterscomprising a first parameter indicating the index/identifier associatedwith the wireless device. For example, the wireless device may receivean RRC release message indicating the wireless device transition from anRRC_CONNECTED state to the RRC_INACTIVE state, wherein the RRC releasemessage may comprise the configuration parameters indicating thewireless device index/identifier. For example, the RRC release messagemay comprise a suspend config IE comprising the configuration parametersindicating the wireless device index/identifier.

In an example, the wireless device may receive broadcast systeminformation (e.g., MIB or a SIB e.g., SIB1) comprising/indicating thewireless device identifier/index. In an example, the wireless device mayreceive paging information via a paging channel, wherein the paginginformation may comprise/indicate the wireless device index/identifier.

The wireless device may transmit, while in RRC_INACTIVE state, an uplinkpacket based on the first timing advance determined form the pluralityof timing advances. The wireless device may transmit the uplink packetbased on the determined timing advance and via a pre-configured resourceor a configured grant resource (e.g., a configured grant Type 1resource).

In an example, the wireless device may receive configuration parametersof a control resource set and/or a search space. The wireless device mayreceive the plurality of timing advance values via the downlink controlchannel/downlink control information received via radio resourcesassociated with the control resource set/search space.

In an example, the wireless device may receive the configurationparameters of the control resource set and/or the search space via oneor more RRC messages. For example, the wireless device may receive anRRC release message, indicating transitioning of the wireless deviceform an RRC_CONNECTED state to an RRC_INACTIVE state, wherein the RRCrelease message may comprise the configuration parameters of the controlresource set and/or the search space. For example, the RRC releasemessage may comprise a suspend config IE comprising the configurationparameters of the control resource set/search space.

In an example, the wireless device may receive paging information via apaging channel. The paging information may indicate the control resourceset and/or the search space or configuration parameters of the controlresource set and/or the search space for receiving the plurality oftiming advance values. For example, the paging information may comprisea paging record associated with the wireless device, wherein the pagingrecord may indicate the control resource set and/or the search space orthe configuration parameters of the control resource set and/or thesearch space. The wireless device may determine the paging record,associated with the wireless device, in the paging information based ona wireless device identifier/RNTI.

In an example, the wireless device may receive broadcast systeminformation (e.g., via a MIB or a SIB e.g., SIB1) wherein the broadcastsystem information may indicate configuration parameters of the controlresource set and/or the search space for receiving the plurality oftiming advance values. The wireless device may determine the controlresource set/search space for receiving the plurality of timing advancevalues based on the configuration parameters indicated by the broadcastsystem information and may receive the plurality of timing advancevalues via the control resource set and/or the search space.

In an example embodiment as shown in FIG. 30, a wireless device in aradio resource control (RRC) inactive state may receive paginginformation via a paging channel. The paging information maycomprise/indicate the timing advance value. The wireless device maytransmit a packet (e.g., via a pre-configured resource or a configuredgrant resource (e.g., a configured grant Type 1 resource)).

In an example, the wireless device may receive configuration parameterscomprising a wireless device identity/RNTI for wireless device operationduring the RRC_INACTIVE state. For example, an RRC release messageindicating a transitioning from the RRC_CONNECTED to the RRC_INACTIVE(e.g., a suspend config IE in the RRC release message) may compriseconfiguration parameters comprising the wireless device identity/RNTI.The configuration parameters may comprise a plurality of wireless deviceidentities/RNTIs (e.g., a full wireless device identity/RNTI and a shortwireless device identity/RNTI). The wireless device may receive paginginformation comprising a paging record associated with the wirelessdevice. The paging record may comprise the wireless device identity/RNTI(e.g., the short wireless device identity/RNTI or the long wirelessdevice identity/RNTI). The wireless device may determine the pagingrecord associated with the wireless device based on the wireless deviceidentity/RNTI. For example, the paging record associated with thewireless device may comprise the timing advance value.

In an example embodiment as shown in FIG. 31, a wireless device in aradio resource control (RRC) inactive state may receive paginginformation via a paging channel. The paging information may indicatescheduling information for receiving a timing advance value. Forexample, the paging information may comprise a field indicating thescheduling information. For example, the paging information may indicatea control resource set and/or search space for receiving a downlinkassignment of a downlink packet, wherein the downlink packet maycomprise the timing advance value. For example, the paging informationmay comprise the configuration parameters of the control resource setand/or the search space for receiving the schedulinginformation/downlink assignment for receiving a downlink packetcomprising the timing advance value. The wireless device may receive thepaging information via the paging channel and may determine the paginginformation and/or scheduling information associated with the wirelessdevice and included in the received paging information based on awireless device identifier/RNTI associated with the wireless device. Forexample, the paging information may comprise a paging record associatedwith the wireless device wherein the paging record may indicate and/ormay comprise configuration parameters of the control resource set and/orthe search space for receiving the scheduling information/downlinkassignment. For example, the paging record may comprise the wirelessdevice identifier/RNTI. The wireless device may receive configurationparameters comprising the wireless device identifier/RNTI. For example,the wireless device may receive an RRC release message indicatingtransitioning of the wireless device from an RRC_CONNECTED state to anRRC_INACTIVE state wherein the RRC release message, or a suspend configIE in the RRC release message, may comprise the wireless deviceidentity/RNTI. The configuration parameters may comprise a shortwireless device identity/RNTI and a long wireless device identity/RNTI.The one or more wireless device identities/RNTIs may be for the wirelessdevice operation in the RRC_INACTIVE state. In an example, the downlinkpacket may comprise a timing advance command MAC CE comprising thetiming advance value.

In an example, the wireless device may receive the paging informationvia the paging channel at a paging occasion. The wireless device mayreceive configuration parameters and may determine the paging occasionsduring the RRC_INACTIVE state based on the configuration parameters. Forexample, the wireless device may receive an RRC release messagecomprising the configuration parameters indicating the paging occasions.The configuration parameters may be received in an RRC release messageor may be included in a suspend config IE in the RRC release message.For example, the wireless device may determine the paging occasionsbased on a periodicity parameter. The configuration parameters,indicating the paging occasions, may comprise the periodicity parameter.

The wireless device may receive the timing advance value based on thescheduling information. The wireless device may receive a downlinkpacket based on the scheduling information, wherein the downlink packetmay comprise a timing advance command MAC CE indicating the timingadvance value. The wireless device may transmit, while in theRRC_INACTIVE state, a packet based on the timing advance value. Forexample, the wireless device may transmit the packet via apre-configured resource or a configured grant resource (e.g., aconfigured grant Type 1 resource).

In an example, a wireless device may receive configuration parameters ofone or more cells comprising a first cell. The one or more cells may begrouped into a timing advance group. In an example, the first cell maybe a primary cell. In an example, the timing advance group may be aprimary timing advance group (e.g., PTAG).

In an example embodiment as shown in FIG. 32, the wireless device mayreceive a first timing advance command MAC CE in an RRC_CONNECTED state.The first timing advance command MAC CE may indicate a first timingadvance value. The first timing advance command MAC CE for uplink timealignment in the RRC_CONNECTED state may have a first format. Thewireless device may transmit a first uplink packet based on the firsttiming advance value indicated by the first timing advance command MACCE. The wireless device may receive an RRC release message indicatingtransitioning from the RRC_CONNECTED state to the RRC_INACTIVE state.For example, a suspend config IE in the RRC release message may indicatethe transitioning from the RRC_CONNECTED state to the RRC_INACTIVE stateand/or suspending the RRC connection for the wireless device. Thewireless device may receive a second timing advance command MAC CE whilein the RRC_INACTIVE state. The second timing advance command MAC CE mayindicate a second timing advance value. The second timing advance MAC CEfor uplink time alignment in the RRC_INACTIVE state may have a secondformat. The wireless device may transmit a second uplink packet based onthe second timing advance value indicated by the second timing advancecommand MAC CE.

In an example, the first format of the first timing advance command MACCE in the RRC_CONNECTED state may comprise a timing advance group (TAG)ID field and the second timing advance command MAC CE in theRRC_INACTIVE state may not comprise a TAG ID field. In an example asshown in FIG. 33, the first timing advance command MAC CE in theRRC_CONNECTED state may comprise a TAG ID field and the second timingadvance command MAC CE in the RRC_INACTIVE state may comprise a fieldwith reserved/pre-configured bits. For example, thereserved/pre-configured bits may be all zeros.

In an example embodiment as shown in FIG. 34, a wireless device in anRRC_CONNECTED state may receive configuration parameters of a configuredgrant configuration. In an example, the configured grant configurationmay be a type 1 configured grant configuration. The wireless device mayactivate a plurality of resources based on receiving the configurationparameters of the configured grant configuration. At least a portion ofthe configuration parameters of the configured grant configuration maybe used for the RRC_CONNECTED state and an RRC_INACTIVE state.

The wireless device may determine a first resource, while in theRRC_CONNECTED state, based on the configured grant configurationparameters. For example, the configured grant configuration parametersmay comprise a periodicity parameter and the wireless device maydetermine a first timing of the first resource based on the periodicityparameter. For example, the configured grant configuration parametersmay comprise one or more parameters indicating frequency domainresources of the first resource. The wireless device may transmit afirst packet via the first resource.

The wireless device may receive an RRC release message indicatingtransitioning from the RRC_CONNECTED state to the RRC_INACTIVE stateand/or suspending an RRC connection for the wireless device. Forexample, the RRC release message may comprise a suspend config IEindicating the transition from the RRC_CONNECTED state to theRRC_INACTIVE state. The wireless device may transition from theRRC_CONNECTED state to the RRC_INACTIVE state based on the receiving theRRC release message.

The wireless device may determine a second resource, while in theRRC_INACTIVE state, based on the configured grant configurationparameters. For example, the configured grant configuration parametersmay comprise a periodicity parameter and the wireless device maydetermine a second timing of the second resource based on theperiodicity parameter. For example, the configured grant configurationparameters may comprise one or more parameters indicating frequencydomain resources of the second resource. The wireless device maytransmit a second packet via the second resource. The wireless devicemay transmit the second packet via the second resource.

The wireless device may determine one or more HARQ parameters fortransmission of the first packet. The wireless device may transmit thefirst packet based on and/or with determining the one or more HARQparameters. The wireless device may not determine the one or more HARQparameters for transmission of the second packet. The wireless devicemay transmit the second packet without determining the one or more HARQparameters.

In an example, the configuration parameters of the configured grantconfiguration may comprise first configuration parameters for theRRC_CONNECTED state and second configuration parameters for theRRC_INACTIVE state. For example, the first configuration parameters maycomprise a first periodicity parameter and the second configurationparameters may comprise a second periodicity parameter. The wirelessdevice may determine the first resource based on the first periodicityparameter and may determine the second resource based on the secondperiodicity parameter. For example, the first configuration parametersmay comprise a parameter indicating a number of HARQ processes and thesecond configuration parameters may not comprise a parameter indicatinga number of HARQ processes. For example, the first configurationparameters may comprise one or more first parameters for determiningconfigured grant resources (e.g., time and frequency domain resources)during the RRC_CONNECTED state and the second configuration parametersmay comprise one or more second parameters for determining configuredgrant resources (e.g., time and frequency domain resources) during theRRC_INACTIVE state.

In an example embodiment as shown in FIG. 35, a wireless device, in anRRC_CONNECTED state, may receive first configuration parameters of afirst configured grant configuration parameters. In an example, theconfigured grant configuration may be a type 1 configured grantconfiguration. The wireless device may activate a plurality of resourcesbased on receiving the configuration parameters of the configured grantconfiguration. The first configuration parameters may be for operationduring the RRC_CONNECTED state and may not be used for operation duringthe RRC_INACTIVE state.

The wireless device may determine a first resource, while in theRRC_CONNECTED state, based on the first configured grant configurationparameters. For example, the first configured grant configurationparameters may comprise a first periodicity parameter and the wirelessdevice may determine a first timing of the first resource based on thefirst periodicity parameter. For example, the first configured grantconfiguration parameters may comprise one or more first parametersindicating frequency domain resources of the first resource. Thewireless device may transmit a first packet via the first resource.

The wireless device may receive an RRC release message indicatingtransitioning from the RRC_CONNECTED state to the RRC_INACTIVE stateand/or suspending an RRC connection for the wireless device. Forexample, the RRC release message may comprise a suspend config IEindicating the transition from the RRC_CONNECTED state to theRRC_INACTIVE state. The wireless device may transition from theRRC_CONNECTED state to the RRC_INACTIVE state based on the receiving theRRC release message. The RRC release message may comprise secondconfiguration parameters of a second configured grant configuration. Thesecond configuration parameters may be for the wireless device duringthe RRC_INACTIVE state. For example, a suspend config IE of the RRCrelease message may comprise the second configuration parameters.

The wireless device may determine a second resource, while in theRRC_INACTIVE state, based on the second configured grant configurationparameters. For example, the second configured grant configurationparameters may comprise a second periodicity parameter and the wirelessdevice may determine a second timing of the second resource based on thesecond periodicity parameter. For example, the second configured grantconfiguration parameters may comprise one or more second parametersindicating frequency domain resources of the second resource. Thewireless device may transmit a second packet via the second resource.The wireless device may transmit the second packet via the secondresource.

The wireless device may determine one or more HARQ parameters fortransmission of the first packet. The wireless device may transmit thefirst packet based on and/or with determining the one or more HARQparameters. The wireless device may not determine the one or more HARQparameters for transmission of the second packet. The wireless devicemay transmit the second packet without determining the one or more HARQparameters.

In an example embodiment as shown in FIG. 36, a wireless device, whilein the RRC_CONNECTED state, may receive first configuration parametersof a first configured grant configuration for the wireless device duringthe RRC_CONNECTED state and second configuration parameters of a secondconfigured grant configuration for the wireless device during anRRC_INACTIVE state. For example, a first parameter in the firstconfiguration parameters may indicate that the first configurationparameters are for the RRC_CONNECTED state and a second parameter in thesecond configuration parameters may indicate the second configurationparameters are for the RRC_INACTIVATE state.

The wireless device may determine a first resource, while in theRRC_CONNECTED state, based on the first configured grant configurationparameters. For example, the first configured grant configurationparameters may comprise a first periodicity parameter and the wirelessdevice may determine a first timing of the first resource based on thefirst periodicity parameter. For example, the first configured grantconfiguration parameters may comprise one or more first parametersindicating frequency domain resources of the first resource. Thewireless device may transmit a first packet via the first resource.

The wireless device may receive an RRC release message indicatingtransitioning from the RRC_CONNECTED state to the RRC_INACTIVE stateand/or suspending an RRC connection for the wireless device. Forexample, the RRC release message may comprise a suspend config IEindicating the transition from the RRC_CONNECTED state to theRRC_INACTIVE state. The wireless device may transition from theRRC_CONNECTED state to the RRC_INACTIVE state based on the receiving theRRC release message.

The wireless device may determine a second resource, while in theRRC_INACTIVE state, based on the second configured grant configurationparameters. For example, the second configured grant configurationparameters may comprise a second periodicity parameter and the wirelessdevice may determine a second timing of the second resource based on thesecond periodicity parameter. For example, the second configured grantconfiguration parameters may comprise one or more second parametersindicating frequency domain resources of the second resource. Thewireless device may transmit a second packet via the second resource.The wireless device may transmit the second packet via the secondresource.

The wireless device may determine one or more HARQ parameters fortransmission of the first packet. The wireless device may transmit thefirst packet based on and/or with determining the one or more HARQparameters. The wireless device may not determine the one or more HARQparameters for transmission of the second packet. The wireless devicemay transmit the second packet without determining the one or more HARQparameters.

In an example, the one or more HARQ parameters may comprise a HARQprocess identifier. The wireless device may determine the HARQ processidentifier for transmission of the first packet based on configuredgrant configuration parameters. In an example, the one or more HARQparameters may comprise a redundancy version. In an example, the one ormore HARQ parameters may comprise a redundancy version. The wirelessdevice may store the first packet, for transmission during theRRC_CONNECTED state, in HARQ buffer associated with a HARQ processidentifier. The wireless device may not store the second packet, fortransmission during the RRC_INACTIVE state, in a HARQ buffer.

In an example, the RRC release message may comprise a suspend config IEindicating the transition from the RRC_CONNECTED state to theRRC_INACTIVE state. The suspend config may comprise configurationparameters for wireless device operation during the RRC_INACTIVE state.The suspend config IE may comprise one or more wireless deviceidentifiers/RNTIs, for example, a full RNTI and a short RNTI. Thetransmitting the second packet during the RRC_INACTIVE state may bebased on a wireless device identifier/RNTI of the one or more wirelessdevice identifiers/RNTIs.

In an example embodiment, a wireless device may receive soundingreference signal (SRS) configuration parameters. The SRS configurationparameters may comprise first configuration parameters for SRStransmission while the wireless device is in an RRC_CONENCTED state andsecond configuration parameters for SRS transmission during anRRC_INACTIVE state. The wireless device may transmit SRS signals duringthe RRC_CONNECTED state using the first configuration parameters and maytransmit SRS signals during the RRC_INACTIVE state use the secondconfiguration parameters.

The wireless device may receive an RRC release message indicatingtransitioning from the RRC_CONNECTED state to the RRC_INACTIVE stateand/or suspending an RRC connection for the wireless device. Forexample, the RRC release message may comprise a suspend config IEindicating the transition from the RRC_CONNECTED state to theRRC_INACTIVE state. The wireless device may transition from theRRC_CONNECTED state to the RRC_INACTIVE state based on the receiving theRRC release message. In an example, the suspend config IE may comprisesecond configuration parameters for SRS transmission during theRRC_INACTIVE state.

In an example, the first configuration parameters may comprise a firstperiodicity and/or offset parameter and the second configurationparameters may comprise a second periodicity and/or offset parameter.The first periodicity and/or offset parameter may be used fordetermining transmission timing of SRS signals during the RRC_CONNECTEDstate and the second periodicity and/or offset parameter may be used fordetermining transmission timing of SRS signals during the RRC_INACTIVEstate.

In an example, the first configuration parameters may comprise one ormore first parameters indicating first resources (e.g., first timing,first comb structure, etc.) for transmitting first SRS signals, duringthe RRC_CONNECTED state, and the second configuration parameters maycomprise second parameters indicating second resources (e.g., secondtiming, second comb structure, etc.) for transmitting second SRSsignals, during the RRC_INACTIVE state.

In an example, the first configuration parameters may comprise one ormore first power control parameters for power calculation of the one ormore first SRS signals, during the RRC_CONNECTED state, and the secondconfiguration parameters may comprise second power control parametersfor power calculation of the one or more second SRS signals, during theRRC_INACTIVE state. The wireless device may transmit the one or morefirst SRS signals using the power levels calculated based on the one ormore first power control parameters and may transmit one or more secondSRS signals using the power levels calculated using the one or moresecond power control parameters.

In an example, the first configuration parameters may comprise one ormore first frequency hopping parameters and the second configurationparameters may comprise one or more second frequency hopping parameters.

The base station may use the transmitted SRS signals during theRRC_INACTIVE state for estimating uplink channel conditions during theRRC_INACTIVE state. The base station may transmit a suspend config IE tothe wireless device to reconfigure one or more parameters during theRRC_INACTIVE and/or for transitioning an RRC state of the wirelessdevice (e.g., to the RRC_CONNECTED state or to the RRC_IDLE state). Forexample, the base station may start a network initiated RRC resumeprocedure and transmit the suspend config IE with new configurationparameters based on the receiving the SRS signals during theRRC_INACTIVE state.

In an example embodiment as shown in FIG. 37, a wireless device may bein an RRC_INACTIVE state. The wireless device may transmit uplink dataduring the RRC_INACTIVE state using a random access process (e.g., atwo-step or a four-step random access process) or based onpre-configured/configured resources (e.g., configured grant Type 1resources). The wireless device may multiplex data from one or morelogical channels corresponding to radio bearers (e.g., data radiobearers and/or signaling radio bearers) in a TB and transmit the TB viathe random access process (e.g., Msg A in two-step random access processor Msg 3 in four-step random access process) or apre-configured/configured resource. For example, for transmission basedon a four-step random access process, the wireless device may receive arandom access response comprising an uplink grant for transmission of apacket. For example, for transmission based on a two-step random accessprocess, the wireless device may transmit a packet in Msg A. Forexample, for transmission based on a pre-configured/configured grantresource, the wireless device may receive configuration parameters ofthe pre-configured/configured grant configuration indicating a pluralityof resources comprising the pre-configured/configured grant resource.For example, the wireless device may receive an RRC release messageindicating transitioning of the wireless device form an RRC_CONNECTEDstate to the RRC_INACTIVE state and/or suspending an RRC connection forthe wireless device, wherein the RRC release message (or a suspendconfig IE in the RRC release message) comprise the configurationparameters of the pre-configured/configured grant configuration. Thewireless device may create a packet based on the configurationparameters and transmit the packet.

The wireless device may employ different multiplexing processes for anuplink transmission based on a random access process and an uplinktransmission based on a pre-configured/configured grant resource. Thewireless device may transmit a first packet (e.g., a first TB) based ona random access process and based on a first multiplexing process. Thewireless device may transmit a second packet (e.g., a second TB) basedon a pre-configured/configured grant resource and based on a secondmultiplexing process.

In an example embodiment as shown in FIG. 38, the first multiplexingprocess, for transmission of the first packet based on the random accessprocess, may include/allow data of one or more logical channels in thefirst packet. The second multiplexing process, for transmission of thesecond packet based on the pre-configured/configured grant resource, mayexclude/disallow data of the one or more logical channels in the secondpacket. In an example, the one or more logical channels may comprise acommon control channel (CCCH) logical channel. The CCCH logical channelmay be mapped to a signaling radio bearer. The CCCH logical channel maybe for transmission of one or more RRC messages (e.g., an RRC resumerequest message, etc.).

In an example, the first multiplexing procedure may comprise a firstlogical channel prioritization (LCP) procedure and the secondmultiplexing procedure may comprise a second LCP procedure. One or moreparameters of the first LCP procedure may be different from one or moreparameters of the second LCP procedure.

For example, the first multiplexing/LCP procedure may comprise a firstlogical channel selection process and the second multiplexing/LCPprocedure may comprise a second logical channel selection process. Thefirst logical channel selection process may select logical channel(s)for the first multiplexing process and for including in the firstpacket. The second logical channel selection process may select logicalchannel(s) for the second multiplexing process and for including in thesecond packet. The first logical channel selection process may selectone or more first logical channels comprising the one or more logicalchannels. The first logical channel selection process may select one ormore first logical channels without excluding the one or more logicalchannels. The second logical channel selection process may select one ormore second logical channels not comprising the one or more logicalchannels. The second logical channel selection process may select one ormore second logical channels with excluding the one or more logicalchannels.

In an example, a wireless device may receive one or more messagescomprising configuration parameters. The one or more messages maycomprise one or more RRC messages. The one or more RRC message maycomprise configuration parameters for the wireless device operationduring an RRC_CONNECTED state. The one or more messages may comprisefirst configuration parameters for wireless device operation during anRRC_INACTIVE state.

In an example embodiment, a wireless device may receive configurationparameters of a logical channel. The configuration parameters maycomprise a first parameter indicating whether the logical channel ismapped to (e.g., is allowed to be transmitted via resources indicatedby) an uplink grant for transmission during an RRC_INACTIVE state. Anexample logical channel configuration with the first parameter (e.g.,RRCInactiveAllowed, other names may be used) is shown in FIG. 39A. In anexample, the first parameter may indicate that the logical channel ismapped to and/or allowed to be transmitted via a resource (e.g., aperiodic resource, pre-configured resource, configured grant/configuredgrant Type 1 resource, resource used during a random access process,e.g., based on uplink grant indicated by RAR or Msg A) in anRRC_INACTIVE state.

In an example embodiment, a wireless device may receive configurationparameters of a logical channel. The configuration parameters maycomprise a first parameter indicating whether the logical channel ismapped to (e.g., is allowed to be transmitted via resources indicatedby) a configured grant or a configured grant Type 1 for transmissionduring an RRC_INACTIVE state. An example logical channel configurationwith the first parameter (e.g., configuredGrantType1RRCInactiveAllowed,other names may be used) is shown in FIG. 39B. In an example, the firstparameter may indicate that the logical channel is mapped to and/orallowed to be transmitted via a pre-configured/configured grant resource(e.g., configured grant Type 1 resource) in an RRC_INACTIVE state.

In an example as shown in FIG. 39A and FIG. 38B, the logical channelconfiguration parameters may further comprise a second parameterindicating that the logical is allowed to be transmitted via aconfigured grant resource (e.g., configured grant Type 1 resource)during the RRC_CONNECTED state. In an example, the configurationparameters may comprise different parameters indicating whether thelogical channel is mapped to/allowed to be transmitted based on aconfigured grant resource (e.g., configured grant Type 1 resource)during the RRC_CONNECTED state and the RRC_INACTIVE state. In anexample, a single parameter may indicate whether the logical channel ismapped to/allowed to be transmitted based on a configured grant resource(e.g., configured grant Type 1 resource) in RRC_CONNECTED andRRC_INACTIVE state.

In an example embodiment, in response to the logical channel beingmapped to/allowed to be transmitted via a resource in RRC_INACTIVEstate, the wireless device may multiplex one or more logical channel,comprising the logical channel, in a packet and transmit the packet viathe resource. In an example as shown in FIG. 40, LC1, LC2 and LC4logical channels are mapped to/allowed to be transmitted via a resourcein RRC_INACTIVE state. For example, the configuration parameters of LC1,LC2 and LC4 may comprise parameters indicating that the LC1, LC2 and LC4are mapped to/allowed to be transmitted via a resource in anRRC_INACTIVE state. The configuration parameters of LC3 may not comprisea parameter indicating that the LC3 logical channel is mapped to/allowedto be transmitted via a resource in the RRC_INACTIVE state. In responseto the logical channel configuration parameters indicating that the LC1,LC2 and LC4 are mapped to/allowed to be transmitted via a resource inRRC_INACTIVE state and LC3 is not mapped to/allowed to be transmittedvia a resource in RRC_INACTIVE state, the wireless device may multiplexdata from LC1, LC2 and LC4 in a packet for transmission via a resourceduring the RRC_INACTIVE state and may exclude LC3. The wireless devicemay transmit the packet based on the resource.

In an example embodiment as shown in FIG. 41, a wireless device mayreceive configuration parameters of a configured grant configuration.The configuration parameters of the configured grant configuration maycomprise one or more first parameters for an RRC_CONNECTED state and oneor more second parameters for an RRC_INACTIVE state. In an example, theconfiguration parameters of the configured grant configuration maycomprise a first information element comprising the one or more firstparameters and a second information element comprising the one or moresecond parameters. The wireless device may transmit a first packet(e.g., a first TB), while in an RRC_CONNECTED state, based on the one ormore first parameters. The wireless device may transmit a second packet(e.g., a second TB), while in an RRC_INACTIVE state, based on the one ormore second parameters.

In an example, the one or more first parameters may comprise one or moreHARQ related parameters and the one or more second parameters may notcomprise a HARQ related parameter. For example, the one or more HARQrelated parameters may comprise a number of HARQ processes. The one ormore first parameters may indicate a number of HARQ processes and theone or more second parameters may not indicate a number of HARQprocesses.

In an example, the one or more first parameters may comprise a firstperiodicity parameter and the one or more second parameters may comprisea second periodicity parameter. The wireless device may determine timeoccasions of first configured grant resources during the RRC_CONNECTEDstate based on the first periodicity parameter. The wireless device maydetermine time occasions of second configured grant resources during theRRC_INACTIVE state based on the second periodicity number. The wirelessdevice may further determine first HARQ process identifiers of the firstconfigured grant transmissions during the RRC_CONNECTED state based onthe first periodicity parameter. The wireless device may not determineHARQ process identifiers for transmissions based on configured grantresources during the RRC_INACTIVE state.

In an example, the one or more first parameters may comprise a firstwireless device identifier/RNTI. The one or more second parameters maycomprise a second wireless device identifier/RNTI. In an example, theone or more second parameters may not comprise a wireless deviceidentifier/RNTI associated with configured grant configuration and maycomprise a wireless device identifier/RNTI associated with wirelessdevice operation in RRC_INACTIVE state.

In an example, the one or more first parameters may comprise a firstrepetition parameter for transmission repetitions during theRRC_CONNECTED state. The wireless device may repeat uplink transmissionscorresponding to the configured grant configuration during theRRC_CONNECTED state based on the first repetition parameter. The one ormore second parameters may comprise a second repetition parameter fortransmission repetitions during the RRC_INACTIVE state. The wirelessdevice may repeat uplink transmissions corresponding to the configuredgrant configuration during the RRC_INACTIVE state based on the secondrepetition parameter.

In an example, the one or more first parameters may comprise a firstpower control parameter for transmissions corresponding to theconfigured grant configuration during the RRC_CONNECTED state. Thewireless device may calculate transmission power levels of configuredgrant uplink transmissions during the RRC_CONNECTED state based on thefirst power control parameter and may transmit the configured grantuplink transmissions during the RRC_CONNECTED state based on thecalculated transmission power levels. The one or more second parametersmay comprise a second power control parameter for transmissionscorresponding to the configured grant configuration during theRRC_INACTIVE state.

In an example embodiment as shown in FIG. 42, a wireless device mayreceive first configuration parameters of a downlink semi-persistentscheduling (SPS) configuration. The downlink SPS configuration may befor receiving timing advance values for uplink transmissions during anRRC_INACTIVE state. For example, the first configuration parameters maycomprise a parameter indicating that the downlink SPS configuration isfor wireless device operation during the RRC_INACTIVE state and/or forreceiving timing advance values during an RRC_INACTIVE state. Thewireless device may activate a plurality of resources, during theRRC_INACTIVE state, based on the receiving the first configurationparameters. The wireless device may activate the plurality of resourcesbased on the receiving the first configuration parameters and withoutreceiving an L1 activation command. The wireless device may receivesecond configuration parameters of a configured grant configuration fortransmitting uplink data packets during an RRC_INACTIVE state. Thewireless device may determine configured grant resources during theRRC_INATIVE state based on the second configuration parameters.

In an example, the wireless device may receive an RRC release messageindicating transitioning of the wireless device to the RRC_INACTIVEstate and/or suspension of an RRC connection for the wireless device.For example, the RRC release message may comprise a suspend config IEindicating the transitioning of the wireless device form theRRC_CONNECTED state to the RRC_INACTIVE state. The suspend config IE maycomprise configuration parameters of the wireless device for thewireless device operation during the RRC_INACTIVE state. For example,the RRC release message or the suspend config IE in the RRC releasemessage may comprise the first configuration parameters of the downlinkSPS configuration and/or the second configuration parameters of theuplink configured grant configuration.

The wireless device may receive timing advance values, during theRRC_INACTIVE state, based on the first configuration parameters. Thewireless device may receive downlink packets based on the firstconfiguration parameters and via the downlink SPS resources, wherein thedownlink packets may comprise the timing advance values. For example,the wireless device may receive timing advance command MAC CEsindicating the timing advance values, wherein the timing advance MAC CEsare multiplexed in the downlink packets. The first configurationparameters may comprise a first periodicity parameter. The wirelessdevice may activate a plurality of downlink assignments based on thefirst periodicity parameter. For example, the wireless device maydetermine time occasions of the plurality of downlink assignments basedon the first periodicity parameter. The wireless device may receive thedownlink packets via the plurality of the downlink assignments.

The wireless device may transmit uplink packets, during the RRC_INACTIVEstate, based on the second configuration parameters and based on thereceived timing advance values. The second configuration parameters maycomprise a second periodicity parameter. The wireless device maydetermine a plurality of pre-configured/configured grant resources basedon the second periodicity parameter. The wireless device may transmitthe uplink packets base don the plurality of thepre-configured/configured grant resources.

In an example embodiment as shown in FIG. 43, a wireless device mayreceive configuration parameters for obtaining timing advance valuesduring an RRC_INACTIVE state. For example, the configuration parametersmay comprise a periodicity parameter. In an example, the wireless devicemay receive an RRC release message indicating wireless device transitionform an RRC_CONNECTED state to an RRC_INACTIVE state, wherein the RRCrelease message may comprise the periodicity parameter. In an example, asuspend config IE of the RRC release message may comprise theperiodicity parameter. In an example the periodicity parameter may be interms of a number of slots or symbols or milliseconds. The wirelessdevice may determine timings for transmissions of random accesspreambles, during RRC_INACTIVE state, based on the periodicityparameter. The wireless device may transmit, during the RRC_INACTIVEstate, random access preambles based on the periodicity parameter and atthe determined timings. In response to the transmissions of the randomaccess preambles, the wireless device may receive timing advance valuesfor uplink transmissions during the RRC_INACTIVE state.

In an example embodiment as shown in FIG. 44, a wireless device maytransmit uplink packets during an RRC_CONNECTED state and anRRC_INACTIVE state. The wireless device may transmit uplink packets,during the RRC_CONNECTED state, based on dynamic or configured grants orbased on random access processes. The wireless device may transmit theuplink packets, during the RRC_INACTIVE state, based on random accessprocesses or based on pre-configured/configured grant resources. Thewireless device may transmit a first uplink packet based on a firstuplink grant during the RRC_CONNECTED state. The wireless device maytransmit the first uplink packet based on a first multiplexing process.The wireless device may multiplex/include one or more MAC CEs in thefirst packet. The wireless device may transmit a second uplink packetbased on a second uplink grant during the RRC_INACTIVE state. Thewireless device may transmit the second packet based on a secondmultiplexing process. The wireless device may not multiplex and/or mayexclude the one or more MAC CEs in the second packet.

In an example embodiment, priorities associated with the one or MAC CEs,for a multiplexing/LCP process, may be different in RRC_CONNECTED stateand the RRC_INACTIVE state. For example, the one or more MAC CEs mayhave a lower priority in the RRC_INACTIVE state compared to theRRC_CONNECTED state. For example, the one or more MACC CEs may havehigher priority than data logical channels in RRC_CONNECTED state andmay have lower priority than data logical channels in RRC_INACTIVEstate. In an example, the one or more MAC CEs may comprise at least oneof BSR and PHR.

In an example embodiment as shown in FIG. 45, a wireless device maytransmit a first MAC CE of a first type via a first uplink grant in anRRC_CONNECTED state. The wireless device may transmit the first MAC CEby multiplexing the first MAC CE in a first packet (e.g., a first TB)and may transmit the first packet based on the first uplink grant. Thefirst type of the first MAC CE may be a BSR or a PHR or another uplinkMAC CE. The wireless device may transmit a second MAC CE of the firsttype via a second uplink grant in an RRC_INACTIVE state. The wirelessdevice may transmit the second MAC CE by multiplexing the second MAC CEin a second packet (e.g., a second TB) and may transmit the secondpacket based on the second uplink grant. Based on the first MAC CE beingtransmitted during the RRC_CONNECTED state, the wireless device maytransit the first MAC CE using a first format for the first type MACCEs. Based on the second MAC CE being transmitted during theRRC_INACTIVE state, the wireless device may transit the second MAC CEusing a second format for the first type MAC CEs.

In an example embodiment as shown in FIG. 46, the first MAC CE of thefirst type may be triggered based on a first trigger condition of one ormore first trigger conditions. The one or more first trigger conditionsmay be for triggering the first type MAC CEs during an RRC_CONNECTEDstate. The second MAC CE may be triggered based on a second triggercondition of one or more second trigger conditions. The one or moresecond trigger conditions may be for triggering the first type MAC CEsduring an RRC_INACTIVE state. In an example, the one or more firsttrigger conditions for triggering the first type MAC CE during anRRC_CONNECTED state may be different from the one or more second triggerconditions for triggering the first type MAC CE during an RRC_INACTIVEstate.

In an example embodiment, a wireless device may receive a first MAC CEof a first type based on first downlink resources in an RRC_CONNECTEDstate. The first type of the first MAC CE may be a downlink MAC CE. Thewireless device may receive a second MAC CE of the first type based onsecond downlink resources in an RRC_INACTIVE state. Based on the firstMAC CE being received during the RRC_CONNECTED state, the wirelessdevice may receive the first MAC CE according to a first format for thefirst type MAC CEs. Based on the second MAC CE being received during theRRC_INACTIVE state, the wireless device may receive the second MAC CEaccording to a second format for the first type MAC CEs.

In an example, a wireless device may receive an RRC release messageindicating transitioning of the wireless device form an RRC_CONNECTEDstate to an RRC_INACTIVE state and/or suspending an RRC connection forthe wireless device. In an example, embodiment, the wireless device mayflush one or more HARQ buffers based on the receiving the RRC releasemessage and/or based on the transitioning from the RRC_CONNECTED stateto the RRC_INACTIVE state and/or suspending the RRC connection. In anexample embodiment, the wireless device may transmit packets stored inthe HARQ buffers via resources (e.g., pre-configured/configured grantresources) during the RRC_INACTIVE state. The wireless device may ignorethe association of the packets stored in the HARQ buffers with HARQprocess identifiers when transmitting the packets via resources duringthe RRC_INACTIVE state. In an example embodiment, the wireless devicemay reset one or more timers associate with the configured grantprocesses (e.g., one or more configured grant timers associated with oneor more HARQ processes) based on the receiving the RRC release messageand/or based on the transitioning from the RRC_CONNECTED state to theRRC_INACTIVE state and/or suspending the RRC connection.

In an example embodiment, a wireless device may receive an RRC releasemessage indicating transitioning from an RRC connected state to an RRCinactive state. The wireless device may start a time alignment timerbased on the receiving the RRC release message. In an example, thewireless device may start the time alignment timer based ontransitioning from the RRC inactive state to the RRC inactive state.

In an example, the starting the time alignment timer may be at a timingoffset to a reference timing.

In an example, the reference timing may be a reference system framenumber (SFN) (e.g., system frame number 0).

In an example, the timing reference may be a first slot/symbol in areference system frame number (e.g., system frame number 0).

In an example, the timing offset may be in terms of a first number ofsymbols.

In an example, the RRC release message may comprise a timing offset. Thestarting the time alignment timer may be based on the timing offset. Inan example, a suspend config IE in the RRC release message may comprisethe timing offset.

In an example embodiment, a wireless device may receive configurationparameters of one or more cells comprising a first cell. The wirelessdevice may receive an RRC release message indicating transitioning ofthe wireless device from an RRC connected state to an RRC inactivestate. The wireless device may determine a timing advance valueassociated with the one or more cells while the wireless device is inthe RRC connected state and before the receiving the RRC releasemessage. In an example, wireless device may determine a timing advancevalue associated with the one or more cells while the wireless device isin the RRC connected state and before the transitioning from the RRCconnected state to the RRC inactive state. The wireless device maytransmit, while in the RRC inactive state and via the first cell, one ormore uplink packets based on the timing advance value.

In an example, the one or more cells may be grouped into a timingadvance group. In an example, the timing advance group may a primarytiming advance group; and the first cell may be a primary cell.

In an example, the transmitting the one or more uplink packets, based onthe timing advance value, may be while a timer is running. In anexample, the timer may be a time alignment timer. In an example, thetimer may be started at a MAC layer. In an example, the timer may bemaintained by a MAC layer. In an example, the timer may be an RRC timerand may be started at the RRC layer. In an example, the timer may be anRRC timer and may be maintained by an RRC layer.

In an example, the RRC release message may comprise a suspend config IEcomprising first configuration parameters for wireless device operationin the RRC inactive state.

In an example, the wireless device may start a timer with a timer valuebased on the receiving the RRC release message. In an example, thewireless device may start a timer based on transitioning from the RRCconnected state to the RRC inactive state. In an example, the RRCrelease message may comprise/indicate the timer value. In an example,the RRC release may comprise a suspend config IE comprising/indicatingthe timer value. The transmitting the one or more uplink packets basedon the timing advance value may be while a timer is running. In anexample, the starting the starting the timer may be at a timing offsetto a reference timing. In an example, the reference timing may be areference system frame number (SFN) (e.g., system frame number 0). In anexample, the reference timing may be a first slot/symbol in a referencesystem frame number (e.g., system frame number 0). In an example, thetiming offset may be in terms of a first number of symbols. In anexample, the RRC release message may comprise/indicate the timingoffset. In an example, a suspend config IE in the RRC release messagemay comprise/indicate the timing offset.

In an example embodiment, a wireless device, in a radio resource control(RRC) connected state, may receive an RRC release message comprising asuspend config information element. The suspend config informationelement may indicate a transition from the RRC connected state to an RRCinactive state. The suspend config information element may compriseconfiguration parameters for wireless device operation in the RRCinactive state. The configuration parameters may comprise one or moreparameters for determining uplink timing for uplink transmission. Thewireless device may transmit, while in the RRC inactive state, uplinkdata based on the one or more parameters.

In an example, the one or more parameters may comprise a timing advancevalue. In an example, the one or more uplink transmissions during theRRC inactive state may be based on the timing advance value. In anexample, the one or more uplink transmissions during the RRC inactivestate may be based on the timing advance value and based on a timerrunning.

In an example, the one or more parameters may comprise a timingalignment timer value for a time alignment timer. In an example, thewireless device may transmit, while in an RRC inactive state, randomaccess preambles based on the time alignment timer. In an example, thewireless device may start a time alignment timer with the time alignmenttimer value based on the receiving the RRC release message. In anexample, the wireless device may start a time alignment timer with thetime alignment timer value based on the transitioning from the RRCconnected state to the RRC inactive state. In an example, the startingthe time alignment timer may be at a timing offset to a referencetiming. In an example, the reference timing may be a reference systemframe number (SFN) (e.g., system frame number 0). In an example, thereference timing may be a first slot/symbol in a reference system framenumber (e.g., system frame number 0). In an example, the timing offsetmay be in terms of a first number of symbols. In an example, the RRCrelease message may indicate the timing offset. In an example, a suspendconfig IE in the RRC release message may indicate the timing offset.

In an example embodiment, a wireless device, in a radio resource control(RRC) inactive state, may transmit a random access preamble forobtaining a timing advance value. The wireless device may receive arandom access response comprising a timing advance value. The wirelessdevice may transmit an RRC resume request message comprising a resumecause information element indicating a cause for RRC resume request as atiming advance request. The wireless device may transmit, while in theRRC inactive state, uplink data based on the timing advance value.

In an example, the transmitting random access preamble may be based onan expiry of a time alignment timer. In an example, the wireless devicemay receive configuration parameters comprising a time alignment timervalue for the time alignment timer. In an example, the wireless devicemay receive an RRC release message comprising the configurationparameters. In an example, the wireless device may receive broadcastsystem information comprising a time alignment timer value for the timealignment timer. In an example, the wireless device may receive paginginformation comprising a time alignment timer value for the timealignment timer.

In an example, the transmitting random access preamble may be based on aperiodicity parameter.

In an example embodiment, a wireless device, in a radio resource control(RRC) inactive state, may start a random access process for obtaining atiming advance value. The wireless device may transmit an RRC resumerequest message comprising a resume cause information element indicatinga cause for RRC resume request as a timing advance request. The wirelessdevice may receive a message comprising a timing advance value. Thewireless device may transmit, while in the RRC inactive state, uplinkdata based on the timing advance value.

In an example, wherein the starting the random access process may bebased on an expiry of a time alignment timer. In an example, thewireless device may receive configuration parameters comprising a timealignment timer value for the time alignment timer. In an example, thewireless device may receive an RRC release message comprising theconfiguration parameters. In an example, the wireless device may receivebroadcast system information comprising the time alignment timer. In anexample, the wireless device may receive paging information comprising atime alignment timer value for the time alignment timer.

In an example, the starting the random access process may be based on aperiodicity parameter.

In an example, the wireless device may receive configuration parameterscomprising/indicating the periodicity parameter.

In an example, the cause information element may further indicate thatthe cause for RRC resume request is not for resuming a suspended RRCconnection.

In an example, the transmitting the uplink data may be via aconfigured/pre-configured resource.

In an example embodiment, a wireless device in a radio resource control(RRC) inactive state, may transmit a random access preamble indicatingthat: the wireless device is requesting a timing advance value; and thewireless device is not requesting resumption of a suspended RRCconnection. The wireless device may receive a random access responsecomprising the timing advance value. In an example, the wireless devicemay receive a message (e.g., Msg B in a two-step random access process)comprising the timing advance value. The wireless device may transmit apacket based on the timing advance value.

In an example, the wireless device may receive configuration parametersindicating one or more random access preambles, comprising the randomaccess preamble, indicating that: the wireless device is requesting atiming advance value; and the wireless device is not requestingresumption of a suspended RRC connection.

In an example, the transmitting random access preamble may be based onan expiry of a timing alignment timer. In an example, the wirelessdevice may receive configuration parameters comprising a time alignmenttimer value for the time alignment timer. In an example, the wirelessdevice may receive an RRC release message comprising the configurationparameters. In an example, the wireless device may receive broadcastsystem information comprising a time alignment timer value for the timealignment timer. In an example, the wireless device may receive paginginformation comprising a time alignment timer value for the timealignment timer.

In an example, the transmitting the random access preamble may be basedon a periodicity parameter. In an example, the wireless device mayreceive receiving parameters comprising/indicating the periodicityparameter.

In an example, the transmitting the packet may be via aconfigured/pre-configured resource.

In an example, the random access response may comprise an uplink grant.A size of the uplink grant may be based on the random access preambleindicating that the wireless device is not requesting resumption of asuspended RRC connection.

In an example embodiment, a wireless device, in a radio resource control(RRC) inactive state, may transmit a random access preamble indicatingwhether the wireless device is requesting resumption of a suspended RRCconnection or not. In an example, a wireless device, in a radio resourcecontrol (RRC) inactive state, may transmit a random access preambleindicating whether the wireless device is requesting an uplink grant fortransmitting UL-CCCH or requesting an uplink for data transmissionwithout UL-CCCH. The wireless device may receive a random accessresponse comprising an uplink grant, wherein a size of the uplink grantis based on the random access preamble. The wireless device may transmita packet based on the uplink grant.

In an example embodiment, a wireless device in a radio resource control(RRC) inactive state, may transmit a random access preamble indicatingthat the wireless device is requesting an uplink grant for transmittingUL-CCCH. The wireless device may receive a random access responsecomprising an uplink grant, wherein the uplink grant is useful fortransmission of UL-CCCH. The wireless device may transmit a packet,comprising data form UL-CCCH, based on the uplink grant.

In an example embodiment, a wireless device may receive a plurality oftiming advance values via a control channel. In an example, the wirelessdevice may receive downlink control information comprising a pluralityof timing advance values. The wireless device may determine a firsttiming advance value in the plurality of timing advance values. Thewireless device may transmit, while in RRC inactive state, uplink databased on the first timing advance value.

In an example, the receiving the control channel/the downlink controlinformation and the transmitting the uplink data may be while thewireless device is in a radio resource control (RRC) inactive state.

In an example, the determining the first timing advance value, in theplurality of timing advance values, may be based on an index/identifierassociated with the wireless device. The wireless device may receiveconfiguration parameters indicating the index/identifier. In an example,the wireless device may receive an RRC release message indicatingtransitioning of the wireless device from an RRC connected state to anRRC inactive state, wherein the RRC release message may comprise theconfiguration parameters. In an example, the RRC release message maycomprise a suspend config information element comprising theconfiguration parameters; and the configuration parameters may be forthe wireless device operation during the RRC inactive state.

In an example, the wireless device may receive configuration parametersof a control resource set and/or a search space, wherein the receivingthe downlink control information/control channel may be via the controlresource set and/or the search space. In an example, the wireless devicemay receive an RRC release message indicating transitioning of thewireless device from an RRC connected state to an RRC inactive state,wherein the RRC release message may comprise the configurationparameters of the control resource set and/or the search space. In anexample, the RRC release message may comprise an RRC suspend configinformation element comprising the configuration parameters of thecontrol resource set and/or the search space.

In an example, the wireless device may receive paging information via apaging channel, the paging information indicating configurationparameters of a control resource set and/or a search space, wherein thereceiving the downlink control information and/or the control channelmay be is via the control resource set and/or the search space.

In an example, the wireless device may receive broadcast systeminformation indicating configuration parameters of a control resourceset and/or search space, wherein the receiving the downlink controlinformation and/or the control channel may be via the control resourceset and/or the search space. In an example, the broadcast systeminformation may be received via a master information block (MIB). In anexample, the broadcast system information may be received via a systeminformation block (SIB). In an example, the SIB may be a SIB 1.

In an example, a search space for receiving the downlink controlinformation and/or the control channel may be a common search space.

In an example, the downlink control information/control channel may beassociated with a first wireless device identifier/RNTI. The wirelessdevice may receive configuration parameters comprising/indicating thewireless device identifier/RNTI. In an example, the wireless device mayreceive an RRC release message comprising a suspend config informationelement. The suspend config information element may comprise theconfiguration parameters. The configuration parameters may be for thewireless device operation during the RRC inactive state.

In an example embodiment, a wireless device, in a radio resource control(RRC) inactive state, may receive paging information via a pagingchannel, the paging information indicating scheduling information forreceiving a timing advance value. The wireless device may receive thetiming advance value based on the scheduling information. The wirelessdevice may transmit a packet based on the timing advance value.

In an example, the scheduling information may indicate radio resourcesand/or a downlink assignment for receiving a downlink packet. Thedownlink packet may comprise the timing advance value. In an example,the downlink packet may comprise a MAC control element indicating thetiming advance value.

In an example, the scheduling information may indicate a controlresource set and/or search space for receiving a downlink assignment ofa downlink packet. The downlink packet may comprise the timing advancevalue. In an example, the wireless device may receive the downlinkpacket based on the downlink assignment. In an example, the downlinkpacket may comprise a MAC control element indicating the timing advancevalue.

In an example, the paging information may comprise a field indicatingthe scheduling information.

In an example, the paging information may comprise a field indicating awireless device identifier/RNTI. In an example, the wireless device mayreceive configuration parameters comprising the wireless deviceidentifier/RNTI.

In an example, the wireless device may receive an RRC release messagecomprising a suspend config information element. The suspend configinformation element may comprise configuration parameters. Theconfiguration parameters may be for the wireless device operation in theRRC inactive state.

In an example, the paging information may comprise a paging recordcomprising a wireless device identifier/RNTI. The paging record mayindicate the scheduling information for the wireless device.

In an example, the receiving the paging information via the pagingchannel may be in a paging occasion. In an example, the paging occasionmay be based on a periodicity. In an example, the wireless device mayreceive configuration parameters indicating the periodicity.

In an example, the wireless device may receive an RRC release messagecomprising the configuration parameters. In an example, a suspend configin an RRC release message may comprise the configuration parameters.

In an example embodiment, a wireless device, in a radio resource control(RRC) inactive state, may receive paging information via a pagingchannel, the paging information indicating a timing advance value forthe wireless device. The wireless device may transmit a packet via aconfigured grant resource and based on the timing advance value.

In an example, the wireless device may receive configuration parameterscomprising a wireless device identity/RNTI, wherein: the paginginformation comprises a paging record comprising the wireless deviceidentity/RNTI; and the paging record comprises/indicates the timingadvance value. In an example, the wireless device may receive an RRCrelease message comprising the configuration parameters. In an example,the RRC release message may comprise a suspend config informationelement comprising a parameter indicating the wireless deviceidentity/RNTI. In an example, the wireless device identity may be a fullwireless device identity/RNTI. In an example, the wireless deviceidentity may be a short wireless device identity/RNTI.

In an example, the receiving the paging information via the pagingchannel may be at a paging occasion. In an example, the paging occasionmay be based on a periodicity. In an example, the wireless device mayreceive configuration parameters indicating the periodicity. In anexample, the wireless device may receive an RRC release messagecomprising the configuration parameters. In an example, a suspend configinformation element in an RRC release message may comprise theconfiguration parameters.

In an example embodiment, a wireless device, in a radio resource control(RRC) connected state, may receive a first timing advance command MAC CEwith a first MAC CE format indicating a first timing advance command.The wireless device may transmit a first uplink packet, in the RRCconnected state, based on the first timing advance command. The wirelessdevice may receive, in an RRC inactive state, a second timing advancecommand MAC CE with a second MAC CE format indicating a second timingadvance command. The wireless device may transmit a second uplinkpacket, in the RRC inactive state, based on the second timing advance.

In an example, the first MAC CE format may comprise a TAG ID field; andthe second MAC CE format may not comprise a TAG ID field.

In an example, the first MAC CE format may comprise a TAG ID field; andthe second MAC CE format may comprise a field comprising reserved bits.In an example, the reserved bits may be all zeros.

In an example embodiment, a wireless device in a radio resource control(RRC) connected state, may receive configuration parameters of aconfigured grant configuration, wherein the configuration parameters maybe used in the RRC connected state and in an RRC inactive state. Thewireless may determine a first resource based on the configured grantconfiguration parameters. The wireless device may transmit a firstpacket via the first resource. The wireless device may receive an RRCrelease message indicating a transition from the RRC connected state tothe RRC inactive state. The wireless device may determine a secondresource based on the configuration parameters. The wireless device maytransmit a second packet via the second resource. The transmitting thefirst packet may be based on and/or with determining one or more HARQparameter. The transmitting the second packet may not be based ondetermining one or more HARQ parameter (e.g., without determining one ormore HARQ parameter).

In an example, the configuration parameters may comprise a periodicityparameter. The determining the first resource may be based on theperiodicity parameter. The determining the second resource may be basedon the periodicity parameter.

In an example, the configuration parameters of the configured grantconfiguration comprise: first configuration parameters for the RRCconnected state; and second configuration parameters for the RRCinactive state. In an example, the determining the first resource may bebased on the first configuration parameters; and the determining thesecond resource may be based on the second configuration parameters.

In an example embodiment, a wireless device, in a radio resource control(RRC) connected state, may receive first configuration parameters of afirst configured grant configuration. The wireless device may determinea first resource based on the first configuration parameters. Thewireless device may transmit a first packet via the first resource. Thewireless device may an RRC release message indicating a transition fromthe RRC connected state to an RRC inactive state, wherein: the RRCrelease message may comprise second configuration parameters of a secondconfigured grant configuration; and the second configuration parametersmay be for the RRC inactive state. The wireless device may determine asecond resource based in the second configuration parameters. Thewireless device may transmit a second packet via the second resource.The transmitting the first packet may be based on and/or withdetermining one or more HARQ parameters. The transmitting the secondpacket may not be based on determining one or more HARQ parameter (e.g.,without determining one or more HARQ parameter).

In an example, the RRC release message may comprise a suspend configinformation element comprising the second configuration parameters of asecond configured grant configuration.

In an example embodiment, a wireless device in a radio resource control(RRC) connected state may receive: first configuration parameters of afirst configured grant configuration for the wireless device in the RRCconnected state; and second configuration parameters of a secondconfigured grant configuration for the wireless device in an RRCinactive state. The wireless device may determine a first resource basedon the first configuration parameters. The wireless device may transmita first packet via the first resource. The wireless device may receivean RRC release message indicating a transition from the RRC connectedstate to an RRC inactive state. The wireless device may determine asecond resource based in the second configuration parameters. Thewireless device may transmit a second packet via the second resource.The transmitting the first packet may be based on and/or withdetermining one or more HARQ parameters. The transmitting the secondpacket may not be based on determining one or more HARQ parameter (e.g.,without determining one or more HARQ parameter).

In an example, the first configuration parameters may comprise a firstperiodicity parameter. The determining the first resource may be basedon the first periodicity parameter. The second configuration parametersmay comprise a second periodicity parameter. The determining the secondresource may be based on the second periodicity parameter.

In an example, the one or more HARQ parameters may comprise a HARQprocess identifier.

In an example, the one or more HARQ parameters may comprise a new dataindicator.

In an example, the one or more HARQ parameters may comprise a redundancyversion.

In an example, the wireless device may store the first packet in a HARQbuffer associated with a HARQ process identifier. The wireless devicemay not store the second packet in a HARQ buffer.

In an example, the RRC release message may comprise a suspend configinformation element comprising one or more configuration parameters forthe RRC inactive state. In an example, the suspend config informationelement may comprise one or more wireless device identifiers (e.g., oneor more radio network temporary identifiers). In an example, the one ormore identifiers/RNTIs may comprise a full inactive state RNTI and ashort inactive state RNTI. In an example, the transmitting the secondpacket may be based on an identifier/RNTI of the one or moreidentifiers/RNTIs.

In an example, the one or more HARQ parameters may comprise a HARQprocess identifier. The determining the HARQ process identifier may bebased on configured grant configuration parameters.

In an example embodiment, a wireless device may receive firstconfiguration parameters for sounding reference signal (SRS)transmission while in a radio resource control (RRC) connected state;and second configuration parameters for SRS transmission while in an RRCinactive state. The wireless device may transmit one or more first SRSsignals based on the first configuration parameters while in the RRCconnected state. The wireless device may transmit one or more second SRSsignals based on the second configuration parameters while in the RRCinactive state.

In a example, the wireless device may receive an RRC release messageindicating transition from the RRC connected state to the RRC inactivestate, wherein the RRC release message may comprise the secondconfiguration parameters. In an example, the RRC release message maycomprise a suspend config information element comprising the secondconfiguration parameters.

In an example, the first configuration parameters may comprise a firstperiodicity and/or offset parameter; and the second configurationparameters may comprise a second periodicity and/or offset parameter.

In an example, the first configuration parameters may comprise one ormore first parameters indicating first resources for transmitting theone or more first SRS signals. The second configuration parameters maycomprise one or more second parameters indicating second resources fortransmitting the one or more second SRS signals.

In an example, the first configuration parameters may comprise one ormore first power control parameters for power calculation of the one ormore first SRS signals. The second configuration parameters comprise oneor more second power control parameters for power calculation of the oneor more second SRS signals.

In an example, the first configuration parameters may comprise one ormore first frequency hopping parameters. The second configurationparameters may comprise one or more second frequency hopping parameters.

In an example embodiment, a wireless device in a radio resource control(RRC) inactive state, may transmit a first packet based on a randomaccess process and using a first multiplexing process. The wirelessdevice, in the RRC inactive state, may transmit a second packet based ona configured grant/preconfigured resource and using on a secondmultiplexing process. The first multiplexing process may include one ormore logical channels in the first packet. The second multiplexingprocess may exclude the one or more logical channels in the secondpacket.

In an example, the one or more logical channels comprise a commoncontrol channel (CCCH) logical channel. In an example, the CCCH logicalchannel may be for transmission of one or more RRC messages. In anexample, the CCCH logical channel may correspond to one or moresignaling radio bearers.

In an example, the wireless device may receive a random access responsecomprising an uplink grant in a four-step random access process, whereinthe transmitting the first packet may be based on the uplink grant.

In an example, the transmitting the first packet may be based on a Msg Ain a two-step random access process.

In an example, the wireless device may receive configuredgrant/pre-configured resource configuration parameters, wherein theconfigured grant/preconfigured resource may be based on the configuredgrant/preconfigured resource configuration parameters. In an example,the wireless device may receive an RRC release message comprising theconfigured grant/preconfigured resource configuration parameters. In anexample, the RRC release message may comprise a suspend configinformation element comprising the configured grant/preconfiguredresource configuration parameters.

In an example, the first multiplexing process may comprise a firstlogical channel selection process selecting one or more first logicalchannels comprising the one or more logical channels. In an example, thefirst multiplexing process may comprise a first logical channelselection process selecting one or more first logical channels withoutexcluding the one or more logical channels. The second multiplexingprocess may comprise a second logical channel selection processselecting one or more second logical channels not comprising the one ormore logical channels. The second multiplexing process may comprise asecond logical channel selection process selecting one or more secondlogical channels excluding the one or more logical channels.

In an example embodiment, a wireless device may receive configurationparameters of a logical channel, the configuration parameters comprisinga first parameter indicating that the logical channel is allowed to betransmitted via a resource in a radio resource control (RRC) inactivestate. The wireless device may transmit a packet, comprising data of thelogical channel, via a resource while the wireless device is in an RRCinactive state.

In an example, the resource may be a periodic resource. In an example,the resource may be a pre-configured resource. In an example, theresource may be a configured grant resource. In an example, theconfigured grant resource may be a configured grant Type 1 resource.

In an example, the configuration parameters may further comprise asecond parameter indicating that the logical channel is allowed to betransmitted via a configured grant resource in an RRC connected state.In an example, the configured resource may be a configured grant type 1resource.

In an example, the wireless device may multiplex one or more logicalchannel, comprising the logical channel, for transmission via theresource.

In an example, the wireless device may determine that the logicalchannel is allowed to be transmitted via the resource based on the firstparameter.

In an example embodiment, a wireless device may receive configurationparameters of a configured grant configuration, the configurationparameters comprising: one or more first configuration parameters for aradio resource control (RRC) connected state; and one or more secondconfiguration parameters for an RRC inactive state. The wireless devicemay transmit a first packet based on the one or more first configurationparameters while the wireless device is in an RRC connected state. Thewireless device may transmit a second packet based on the one or moresecond configuration parameters while the wireless device is in an RRCinactive state.

In an example, the configuration parameters of the configured grantconfiguration may comprise a first information element comprising theone or more first configuration parameters and a second informationelement comprising the second configuration parameters.

In an example, the first configuration parameters may indicate a numberof HARQ processes. The second configuration parameters may not indicatea number of HARQ processes.

In an example, the first configuration parameters comprise a firstperiodicity parameter. The second configuration parameters may comprisea second periodicity parameter.

In an example, the first configuration parameters may comprise a firstwireless device identifier/RNRI. The second configuration parameters maycomprise a second wireless device identifier/RNTI.

In an example, the first configuration parameters may comprise a firstrepetition parameter. The second configuration parameters may comprise asecond repetition parameter.

In an example, the first configuration parameters may comprise arepetition parameter. The second configuration parameters may notcomprise a repetition parameter.

In an example, the first configuration parameters may comprise a firstpower control parameter. The second configuration parameters maycomprise a second power control parameter.

In an example embodiment, a wireless device may receive firstconfiguration parameters of a downlink semi-persistent scheduling (SPS)configuration for receiving timing advance values for uplinktransmissions during a radio resource control (RRC) inactive state; andsecond configuration parameters of a configured grant configuration fortransmitting uplink data packets during an RRC inactive state. Thewireless device may receive a timing advance value based on the firstconfiguration parameters. The wireless device may transmit an uplinkdata packet based on the timing advance value and based on the secondconfiguration parameters.

In an example, the wireless device may receive an RRC release messagecomprising at least one of the first configuration parameters and thesecond configuration parameters. In an example, the RRC release messagemay comprise a suspend config information element comprising the firstconfiguration parameters and the second configuration parameters.

In an example, the wireless device may activate a plurality of resourcesfor receiving the timing advance values based on the receiving the firstconfiguration parameters. The wireless device may activate a pluralityof resources, without receiving a physical layer activation, forreceiving the timing advance values based on the receiving the firstconfiguration parameters.

In an example, the timing advance value may be received via a downlinkpacket. In an example, the downlink packet may comprise a MAC CEcomprising the timing advance value.

In an example, the first configuration parameters may indicate a firstperiodicity. The first configuration parameters may indicate a pluralityof downlink assignments based on the first periodicity. The time advancevalues may be received via the plurality of downlink assignments.

In an example, the second configuration parameters may indicate a secondperiodicity. The second configuration parameters may indicate aplurality of configured grant/preconfigured resources for transmissionof uplink data packets.

In an example embodiment, a wireless device may receive configurationparameters comprising a periodicity parameter for obtaining timingadvance values. The wireless device may transmit random access preamblesin a radio resource control (RRC) inactive state and based on theperiodicity parameter. The wireless device may receive the timingadvance values based on the transmitting the random access preambles.The wireless device may transmit uplink packets based on the timingadvance values.

In an example embodiment, a wireless device in a radio resource control(RRC) connected state, may transmit a first packet based on a firstuplink grant and using a first multiplexing process. The wireless devicemay transmit, in an RRC inactive state, a second packet based on asecond uplink grant and using on a second multiplexing process. Thefirst multiplexing process may include one or more MAC CEs in the firstpacket. The second multiplexing process may exclude the one or more MACCEs in the second packet.

In an example, the one or more MAC CEs may comprise at least one of BSRand PHR.

In an example embodiment, a wireless device may transmit, in a radioresource control (RRC) connected state, a first packet comprising afirst BSR MAC CE. The wireless device may transmit, in an RRC inactivestate, a second packet comprising a second BSR MAC CE. The first BSR MACCE may be based on a first format. The second BSR MAC CE may be based ona second format.

In an example embodiment, a wireless device may transmit, in a radioresource control (RRC) connected state, a first packet comprising afirst PHR MAC CE. The wireless device may transmit, in an RRC inactivestate, a second packet comprising a second PHR MAC CE. The first PHR MACCE may be based on a first format. The second PHR MAC CE may be based ona second format.

In an example embodiment, a wireless device may transmit, in a radioresource control (RRC) connected state, a first packet comprising afirst BSR MAC CE. The wireless device may transmit, in an RRC inactivestate, a second packet comprising a second BSR MAC CE. The first BSR MACCE may be triggered based on a first trigger in one or more firsttrigger conditions. The second BSR MAC CE may be triggered based on asecond trigger in one or more second trigger conditions.

In an example embodiment, a wireless device may transmit, in a radioresource control (RRC) connected state, a first packet comprising afirst PHR MAC CE. The wireless device may transmit, in an RRC inactivestate, a second packet comprising a second PHR MAC CE. The first PHR MACCE may be triggered based on a first trigger in one or more firsttrigger conditions. The second PHR MAC CE may be triggered based on asecond trigger in one or more second trigger conditions.

A wireless device in an RRC inactive state may have to resume theconnection (e.g., move to an RRC connected state) for DL (e.g., mobileterminate (MT)) and UL (e.g., mobile originated (MO)) data. Connectionsetup and subsequently release to the RRC inactive state may occur foreach data transmission even for small and infrequent data packets. Thismay result in unnecessary power consumption and signaling overhead.Existing solutions for small data transmission during the RRC inactivestate may be inefficient and may lead to degraded wireless device andwireless network performance. Example embodiments enhance wirelessdevice and wireless network performance during the RRC inactive state.

In an example embodiment as shown in FIG. 47, a wireless device be in anRRC connected state. The wireless device may have an RRC connection witha base station. The wireless device may be served by one or more cellsprovided by one or more base stations. The wireless device may receivean RRC release message. The RRC release message may indicatetransitioning of the wireless device to an RRC Inactive state. Forexample, the RRC release message may comprise a suspend config IEcomprising one or more first configuration parameters indicatingtransitioning of the wireless device from the RRC connected state to theRRC inactive state. The one or more first configuration parameters maybe used by the wireless device for operation during the RRC inactivestate. For example, the one or more first configuration parameters maycomprise one or more RNTIs (e.g., a fullI-RNTI and/or a shortI-RNTI) foroperation during the RRC inactive state, a ran-PagingCycle parameterindicating a wireless device-specific cycle for RAN-initiated paging, atimer (e.g., t380) indicating a timer that triggers the periodic RNAUpdate procedure in wireless device, a RAN notification area informationparameter, etc. The RRC release message (for example the suspendconfigIE in the RRC release message) may further comprise one or more secondconfiguration parameters of a configured grant configuration. Theconfigured grant configuration may be for transmissions by the wirelessdevice during the RRC inactive state. The configured grant configurationmay be a Type 1 configured grant configuration and the wireless devicemay activate a plurality of configured grants in response to receivingthe RRC release message and based on the one or more secondconfiguration parameters. The wireless device may activate the pluralityof configured grants in response to receiving the RRC release messageand without receiving an activation DCI. The RRC release message mayfurther comprise one or more third configuration parameters of a timealignment timer. The one or more third configuration parameters mayindicate a time alignment timer value of the time alignment timer. Thewireless device may use the time alignment timer and may determinewhether the uplink of the wireless device is time-aligned or not, duringthe RRC inactive state, based on the time alignment timer running or notrunning. For example, the wireless device may release the configuredgrant configuration and/or deactivate configured grants associated withthe configured grant configuration in response to the time alignmenttimer not running. In an example, the suspend config IE of the RRCrelease message may comprise the one or more first configurationparameters, the one or more second configuration parameters and the oneor more third configuration parameters.

In response to receiving the RRC release message, the wireless devicemay start the time alignment timer. The wireless device may start thetime alignment timer based on the one or more third configurationparameters, included in the RRC release message, in response toreceiving the RRC release message. The wireless device may start thetime alignment timer in response to receiving the RRC release messageand the RRC release message comprising the one or more thirdconfiguration parameters of the time alignment timer. For example, theone or more third configuration parameters may comprise a time alignmenttimer value and the wireless device may start the time alignment timerwith the time alignment timer value. In an example, the wireless devicemay determine a first timing, after the reception timing of the RRCrelease message, to start the time alignment timer. The wireless devicemay start the time alignment timer in the first timing, wherein thefirst timing may be based on a reference timing. For example, thereference timing may be based on a system frame number (SFN) (e.g., SFN0). For example, the first timing may be an offset (e.g., in a firstnumber of symbols/slots) to the reference timing. In an example, the RRCrelease message (e.g., the suspend config IE in the RRC release message)may comprise a parameter indicating the offset (e.g., indicating thenumber of symbols/slots).

While in the RRC inactive state and based on the time alignment timer,associated with the inactive state, running, the wireless device maytransmit a transport block based on a first configured grant associatedwith the configured grant configuration. The wireless device maydetermine radio resources of the configured grant based on theconfiguration parameters and may transmit the transport block via thedetermined radio resources. The wireless device may multiplex one ormore logical channels in the transport block based on amultiplexing/logical channel prioritization procedure. The wirelessdevice may select the one or more logical channels for multiplexing inthe transport block based on the one or more logical channels beingconfigured for/allowed for transmission in the RRC inactive state. Forexample, the wireless device may receive configuration parameters of theone or more logical channels indicating that the one or more logicalchannels are allowed/configured for transmission during the RRC inactivestate. For example, the configuration parameters of the one or morelogical channels may indicate that the one or more logical channels areallowed/configured for transmission during the RRC inactive state andbased configured grants.

The wireless device may transmit the transport block based on a timingadvance value. In an example, the wireless device may determine thetiming advance associated with the transport block based on a parameterin in the RRC release message. For example, the RRC release message maycomprise a parameter indicating a timing advance value and uplinktransmissions (e.g., transmissions based on configured grants) duringthe RRC inactive state, while the time alignment timer is running, maybe based on the timing advance value.

In an example, the wireless device may determine the timing advancevalue as timing advance value used by the wireless device on or beforereception of the RRC release message. The wireless device may start thetime alignment timer value in response to receiving the RRC releasemessage and may perform uplink transmissions (e.g., uplink transmissionsbased on configured grants) based on the timing advance value and whilethe time alignment timer is running.

While in the RRC inactive state, the wireless device may receive atiming advance command (e.g., via a RAR message in a random accessprocess or based on a timing advance MAC CE or based on an RRC message(e.g., a parameter in an RRC release message may indicate the timingadvance)). The timing advance command may indicate a timing advancevalue. The wireless device may start the time alignment timer inresponse to receiving the timing advance command. The wireless devicemay start the time alignment timer with the time alignment timer value(e.g., the time alignment timer value indicated by the one or more thirdconfiguration parameters included in the RRC release message). Thewireless device may transmit a second transport block, e.g., based on asecond configured grant, and based on the timing advance value indicatedby the timing advance command.

In an example embodiment as shown in FIG. 48, a wireless device may bein an RRC inactive state. The wireless device may transition from an RRCconnected state to the RRC inactive state in response to receiving anRRC release message. For example, the RRC release message may comprise asuspend config IE comprising configuration parameters for wirelessdevice operation during the RRC inactive state. In an example, thewireless device may perform uplink transmissions during the RRC inactivestate based on a time alignment timer, associated with the RRC inactivestate, running. For example, the RRC release message may compriseconfiguration parameters of the time alignment timer indicating a timealignment timer value for the time alignment timer and the wirelessdevice may start the time alignment timer with the time alignment timervalue in response to receiving the RRC release message. In an example,the time alignment timer may expire. The wireless device may transmit aresume request message comprising a cause IE, wherein a value of thecause IE may indicate a timing advance request. For example, the causeIE may indicate that the cause of the resume request message is forobtaining/receiving the timing advance value and not for resuming theRRC connection. For example, the wireless device may transmit the resumerequest message based on a random access message of a random accessprocess. For example, the wireless device may transmit the resumerequest message based on a Msg 3 of four-step random access process or aMsg A of a two-step random access process. In an example, the wirelessdevice may transmit the resume request message in response to the timealignment timer expiring. The wireless device may receive a timingadvance value in response to transmitting the resume request message.For example, the wireless device may receive the timing advance value ina Msg 2 (e.g., RAR) of the four-step random access process or a Msg B ofthe two-step random access process. For example, the RAR or the Msg Bmay comprise a field with a value indicating the timing advance value.The wireless device may transmit a transport block based on the timingadvance value while in the RRC inactive state. In an example, thewireless device may transmit the transport block based on a configuredgrant.

In an example embodiment as shown in FIG. 49, a wireless device may awireless device may be in an RRC inactive state. The wireless device maytransition from an RRC connected state to the RRC inactive state inresponse to receiving an RRC release message. For example, the RRCrelease message may comprise a suspend config IE comprisingconfiguration parameters for wireless device operation during the RRCinactive state. The wireless device may perform small data transmissionsduring the RRC inactive state based on performing random accessprocesses. For example, the wireless device may transmit a random accesspreamble for small data transmission during the RRC inactive state. Thewireless device may select the random access preamble based on a size ofan uplink grant requested to be received in a RAR/MsgB in response totransmitting the random access preamble. The wireless device maydetermine the size of the requested uplink grant based on a size of anuplink common control channel (UL-CCCH) for transmission of an RRCmessage to be transmitted based on the uplink grant. For example, thewireless device may select the random access preamble from one or morefirst preambles based on the requested uplink grant size being smallerthan or equal to a first size. For example, the wireless device mayselect the random access preamble from one or more second preamblesbased on the requested uplink grant size being larger than or equal tothe first size. In an example, a plurality of random access preamblesmay be partitioned to a plurality of sets of random access preambles andeach set of random access preamble may be associated with a size of arequested uplink grant. In response to receiving the uplink grant (e.g.,in a RAR), the wireless device may transmit a transport block based onthe uplink grant. The wireless device may multiplex one or more logicalchannels comprising an uplink common control channel logical channel ina transport block and may transmit the transport block.

In accordance with various exemplary embodiments in the presentdisclosure, a device (e.g., a wireless device, a base station and/oralike) may include one or more processors and may include memory thatmay store instructions. The instructions, when executed by the one ormore processors, cause the device to perform actions as illustrated inthe accompanying drawings and described in the specification. The orderof events or actions, as shown in a flow chart of this disclosure, mayoccur and/or may be performed in any logically coherent order. In someexamples, at least two of the events or actions shown may occur or maybe performed at least in part simultaneously and/or in parallel. In someexamples, one or more additional events or actions may occur or may beperformed prior to, after, or in between the events or actions shown inthe flow charts of the present disclosure.

FIG. 50 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 5010, a wirelessdevice may receive a radio resource control (RRC) release messagecomprising: one or more first configuration parameters indicatingtransitioning from an RRC connected state to an RRC inactive state; oneor more second configuration parameters of a configured grantconfiguration associated with small data transmission in the RRCinactive state; and one or more third configuration parameters of a timealignment timer associated with small data transmission in the RRCinactive state. At 5020, the wireless device may start the timealignment timer in response to receiving the RRC release message andbased on the one or more third configuration parameters. At 5030, thewireless device may transmit a transport block while in the RRC inactivestate: based on radio resources of a first configured grant associatedwith the configured grant configuration; and based on the time alignmenttimer running.

In an example embodiment, the one or more third configurationparameters, received by the wireless device at 5010, may indicate a timealignment timer value of the time alignment timer. The starting the timealignment timer, at 5020, may be with the time alignment timer value.

In an example embodiment, the transmitting the transport block, at 5030,may further be based on a timing advance value. In an exampleembodiment, the wireless device may determine the timing advance value.In an example embodiment, the determining the timing advance value maybe based on a first timing advance value used by the wireless devicebefore receiving the RRC release message. In an example embodiment, theRRC release message, received at 5010, may comprise a parameterindicating the timing advance value. In an example embodiment, the RRCrelease message may comprise a suspend config information elementcomprising the parameter.

In an example embodiment, the wireless device may activate, a pluralityof configured grants, comprising the first configured grant, associatedwith the configured grant configuration in response to receiving the RRCrelease message, at 5010, and based on the one or more secondconfiguration parameters. In an example embodiment, the activating theplurality of configured grants may be in response to receiving the RRCrelease message, at 5010, and without reception of an activationdownlink control information.

In an example embodiment, the configured grant configuration, for whichthe one or more second configuration parameters may be received at 5010,may be a type 1 configured grant.

In an example embodiment, the starting the time alignment timer, at5020, may be based on a reference timing. In an example embodiment, thestarting the time alignment timer, at 5020, may be based on an offset tothe reference timing. In an example embodiment, the offset may be in afirst number of symbols. In an example embodiment, the RRC releasemessage, received at 5010, may comprise a parameter indicating theoffset and/or the first number. In an example embodiment, the RRCrelease message, received at 5010, may comprise a suspend configinformation element comprising a parameter indicating the offset and/orthe first number. In an example embodiment, the reference timing may bebased on a system frame number. In an example embodiment, the systemframe may be system frame zero.

In an example embodiment, the wireless device may receive a timingadvance command indicating a first timing advance. The wireless devicemay start the time alignment timer based on the receiving the timingadvance command. In an example embodiment, the wireless device maytransmit a second transport block based on radio resources of a secondconfigured grant and based on the first timing advance.

In an example embodiment, the wireless device may multiplex one or morelogical channels in the transport block wherein the one or more logicalchannels are configured for transmission of small data in the RRCinactive state.

In an example embodiment, the RRC release message, received at 5010, maycomprise a suspend config information element comprising the one or morefirst configuration parameters, the one or more second configurationparameters and the one or more third configuration parameters.

FIG. 51 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 5110, a wirelessdevice may receive a radio resource control (RRC) release messageindicating transitioning from an RRC connected state to an RRC inactivestate, wherein the RRC release message may comprise one or more firstconfiguration parameters of a time alignment timer associated with smalldata transmission in the RRC inactive state. At 5120, the wirelessdevice may start the time alignment timer in response to receiving theRRC release message and based on the one or more first configurationparameters. At 5130, the wireless device may transmit a transport blockwhile in the RRC inactive state and based on the time alignment timerrunning.

In an example embodiment, the RRC release message, received at 5110, mayfurther comprise one or more second configuration parameters of aconfigured grant configuration, wherein the transmitting the transportblock may be based on a configured grant associated with the configuredgrant configuration.

FIG. 52 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 5210, a wirelessdevice may transmit, in a radio resource control (RRC) inactive state, aresume request message comprising a cause information element with avalue indicating a timing advance request. At 5220, the wireless devicemay receive a timing advance value. At 5230, the wireless device maytransmit a transport block based on the received timing advance value.

In an example embodiment, the transmitting the resume request message,at 5210, may be based on an expiry of a time alignment timer.

In an example embodiment, the wireless device may receive an RRC releasemessage comprising a parameter indicating a time alignment timer value.The wireless device may start a time alignment timer with the timealignment timer value.

In an example embodiment, the transmitting the resume request message,at 5210, may be based on a random access message of a random accessprocess. In an example embodiment, the random access process may be afour-step random access process. The random access message may be aMessage 3 of the four-step random access process. In an exampleembodiment, the random access process may be a two-step random accessprocess. The random access message may be a Message A of the two-steprandom access process. In an example embodiment, the random accessprocess may be a four-step random access process. The receiving thetiming advance value, at 5220, may be based on a Message 2 (e.g., RAR)of the four-step random access process. In an example embodiment, therandom access process may be a two-step random access process. Thereceiving the timing advance value may be based on a Message B of thetwo-step random access process. In an example embodiment, a randomaccess response message or the Msg B, of the random access process, maycomprise a field indicating the timing advance value.

In an example embodiment, the value of the cause information element, inthe resume request message transmitted at 5210, may further indicatethat the cause of the RRC resume request is not for resuming a suspendedRRC connection.

In an example embodiment, the transmitting the transport block may bewhile the wireless device is in the RRC inactive state.

FIG. 53 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 5310, a wirelessdevice may transmit, in a radio resource control (RRC) inactive state, arandom access preamble for small data transmission in the RRC inactivestate. At 5320, the wireless device may receive a random access responsecomprising an uplink grant, wherein a size of the uplink grant is basedon the random access preamble. At 5330, the wireless device may transmita transport block, comprising data of an uplink common control channellogical channel, based on the uplink grant.

FIG. 54 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 5410, a wirelessdevice may receive, in a radio resource control (RRC) inactive state, aplurality of timing advance values via a control channel. At 5420, thewireless device may determine a first timing advance value in theplurality of timing advance values. At 5430, the wireless device maytransmit, while in RRC inactive state, a transport block based on thefirst timing advance value.

In an example embodiment, the plurality of timing advance values,received at 5410, may be received in a downlink control information.

In an example embodiment, the determining the first timing value in theplurality of timing advance values, at 5420, may based on anindex/identifier associated with the wireless device.

FIG. 55 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 5510, a wirelessdevice may receive, in a radio resource control (RRC) inactive state,paging information via a paging channel, wherein the paging informationis associated with a timing advance value. At 5520, the wireless devicemay transmit, while in the RRC inactive state, a transport block basedon the timing advance value.

In an example embodiment, the paging information, received at 5510, mayindicate scheduling information for receiving the timing advance value.In an example embodiment, the wireless device may receive the timingadvance value based on the scheduling information.

In an example embodiment, the paging information may indicate the timingadvance value.

FIG. 56 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 5610, a wirelessdevice, in a radio resource control (RRC) connected state, may receive afirst timing advance command medium access control (MAC) control element(CE), with a first MAC CE format, indicating a first timing advancecommand. At 5620, the wireless device may transmit a first uplinktransport block, in the RRC connected state, based on the first timingadvance command. At 5630, the wireless device, in an RRC inactive state,may receive a second timing advance command MAC CE, with a second MAC CEformat, indicating a second timing advance command. At 5640, thewireless device may transmit a second uplink transport block, in the RRCinactive state, based on the second timing advance command.

FIG. 57 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 5710, a wirelessdevice, in a radio resource control (RRC) inactive state, may transmit afirst transport block based on a random access process and using a firstmultiplexing process. At 5720, the wireless device, in the RRC inactivestate, may transmit a second transport block based on a configured grantresource and using a second multiplexing process. The first transportblock may comprise one or more logical channels based on the firstmultiplexing process. The second transport block may not comprise theone or more logical channels based on the second multiplexing process.

In an example embodiment, the one or more logical channels may beexcluded from the second transport block based on the secondmultiplexing process.

FIG. 58 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 5810, a wirelessdevice, may receive configuration parameters of a logical channel, theconfiguration parameters comprising a first parameter indicating thatthe logical channel is allowed to be transmitted in a radio resourcecontrol (RRC) inactive state. At 5820, the wireless device may transmita transport block, comprising data of the logical channel, while thewireless device is in the RRC inactive state.

FIG. 59 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 5910, a wirelessdevice may receive first configuration parameters and secondconfiguration parameters. The first configuration parameters may be of adownlink semi-persistent scheduling (SPS) configuration for receivingtiming advance values for uplink transmissions during a radio resourcecontrol (RRC) inactive state. The second configuration parameters may beof a configured grant configuration for transmitting uplink transportblocks during an RRC inactive state. At 5920, the wireless device mayreceive a timing advance value based on the first configurationparameters. At 5930, the wireless device may transmit an uplinktransport block based on the timing advance value and based on thesecond configuration parameters.

FIG. 60 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 6010, a wirelessdevice may receive configuration parameters comprising a periodicityparameter for obtaining timing advance values. At 6020, the wirelessdevice may transmit random access preambles in a radio resource control(RRC) inactive state and based on the periodicity parameter. At 6030,the wireless device may receive the timing advance values based on thetransmitting the random access preambles. At 6040, the wireless devicemay transmit uplink transport blocks, in the RRC inactive state, basedon the timing advance values.

FIG. 61 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 6110, a wirelessdevice in a radio resource control (RRC) connected state, may transmit afirst transport block based on a first uplink grant using a firstmultiplexing process. At 6120, the wireless device in an RRC inactivestate, may transmit a second transport block based on a second uplinkgrant and using on a second multiplexing process. Based on the firstmultiplexing process, the first transport block may comprise one or moremedium access control (MAC) control elements (CEs). Based on the secondmultiplexing process, the second transport block may not comprise theone or more MAC CEs.

In an example embodiment, the one or more MAC CEs may be excluded fromthe second transport block based on the second multiplexing process.

In an example embodiment, the first multiplexing process may be used inthe RRC connected state. The second multiplexing process may be used inthe RRC inactive state.

FIG. 62 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 6210, a wirelessdevice, in a radio resource control (RRC) connected state, may transmita first transport block comprising a first medium access control (MAC)control element (CE) of a first type. At 6220, the wireless device, inan RRC inactive state, may transmit a second transport block comprisinga second MAC CE of the first type. The first MAC CE of the first typemaybe of a first format. The second MAC CE of the first type may be of asecond format.

In an example embodiment, the first type of MAC CE may be a bufferstatus report.

In an example embodiment, the first type of MAC CE may be a powerheadroom report.

In an example embodiment, the first MAC CE of the first type may be ofthe first format based on transmitting the first MAC CE, at 6210, in theRRC connected state.

In an example embodiment, the second MAC CE of the first type may be ofthe second format based on transmitting the second MAC CE, at 6220, inthe RRC inactive state.

FIG. 63 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 6310, a wirelessdevice, in a radio resource control (RRC) connected state, may transmita first transport block comprising a first medium access control (MAC)control element (CE) of a first type. At 6320, the wireless device, inan RRC inactive state, may transmit a second transport block comprisingthe second MAC CE of the first type. The first MAC CE of the first typemay be triggered based on one or more first trigger conditions. Thesecond MAC CE of the first type may be triggered based on one or moresecond trigger conditions.

In an example embodiment, the first type of MAC CE may be a bufferstatus report.

In an example embodiment, the first type of MAC CE may be a powerheadroom report.

In an example embodiment, the first MAC CE of the first type may betriggered based on the one or more first trigger conditions based ontransmitting the first MAC CE, at 6210, in the RRC connected state.

In an example embodiment, the second MAC CE of the first type may betriggered based on the one or more second trigger conditions based ontransmitting the second MAC CE, at 6220, in the RRC inactive state.

Various exemplary embodiments of the disclosed technology are presentedas example implementations and/or practices of the disclosed technology.The exemplary embodiments disclosed herein are not intended to limit thescope. Persons of ordinary skill in the art will appreciate that variouschanges can be made to the disclosed embodiments without departure fromthe scope. After studying the exemplary embodiments of the disclosedtechnology, alternative aspects, features and/or embodiments will becomeapparent to one of ordinary skill in the art. Without departing from thescope, various elements or features from the exemplary embodiments maybe combined to create additional embodiments. The exemplary embodimentsare described with reference to the drawings. The figures and theflowcharts that demonstrate the benefits and/or functions of variousaspects of the disclosed technology are presented for illustrationpurposes only. The disclosed technology can be flexibly configuredand/or reconfigured such that one or more elements of the disclosedembodiments may be employed in alternative ways. For example, an elementmay be optionally used in some embodiments or the order of actionslisted in a flowchart may be changed without departure from the scope.

An example embodiment of the disclosed technology may be configured tobe performed when deemed necessary, for example, based on one or moreconditions in a wireless device, a base station, a radio and/or corenetwork configuration, a combination thereof and/or alike. For example,an example embodiment may be performed when the one or more conditionsare met. Example one or more conditions may be one or moreconfigurations of the wireless device and/or base station, traffic loadand/or type, service type, battery power, a combination of thereofand/or alike. In some scenarios and based on the one or more conditions,one or more features of an example embodiment may be implementedselectively.

In this disclosure, the articles “a” and “an” used before a group of oneor more words are to be understood as “at least one” or “one or more” ofwhat the group of the one or more words indicate. The use of the term“may” before a phrase is to be understood as indicating that the phraseis an example of one of a plurality of useful alternatives that may beemployed in an embodiment in this disclosure.

In this disclosure, an element may be described using the terms“comprises”, “includes” or “consists of” in combination with a list ofone or more components. Using the terms “comprises” or “includes”indicates that the one or more components are not an exhaustive list forthe description of the element and do not exclude components other thanthe one or more components. Using the term “consists of” indicates thatthe one or more components is a complete list for description of theelement. In this disclosure, the term “based on” is intended to mean“based at least in part on”. The term “based on” is not intended to mean“based only on”. In this disclosure, the term “and/or” used in a list ofelements indicates any possible combination of the listed elements. Forexample, “X, Y, and/or Z” indicates X; Y; Z; X and Y; X and Z; Y and Z;or X, Y, and Z.

Some elements in this disclosure may be described by using the term“may” in combination with a plurality of features. For brevity and easeof description, this disclosure may not include all possiblepermutations of the plurality of features. By using the term “may” incombination with the plurality of features, it is to be understood thatall permutations of the plurality of features are being disclosed. Forexample, by using the term “may” for description of an element with fourpossible features, the element is being described for all fifteenpermutations of the four possible features. The fifteen permutationsinclude one permutation with all four possible features, fourpermutations with any three features of the four possible features, sixpermutations with any two features of the four possible features andfour permutations with any one feature of the four possible features.

Although mathematically a set may be an empty set, the term set used inthis disclosure is a nonempty set. Set B is a subset of set A if everyelement of set B is in set A. Although mathematically a set has an emptysubset, a subset of a set is to be interpreted as a non-empty subset inthis disclosure. For example, for set A={subcarrier1, subcarrier2}, thesubsets are {subcarrier1}, {subcarrier2} and {subcarrier1, subcarrier2}.

In this disclosure, the phrase “based on” may be used equally with“based at least on” and what follows “based on” or “based at least on”indicates an example of one of plurality of useful alternatives that maybe used in an embodiment in this disclosure. The phrase “in response to”may be used equally with “in response at least to” and what follows “inresponse to” or “in response at least to” indicates an example of one ofplurality of useful alternatives that may be used in an embodiment inthis disclosure. The phrase “depending on” may be used equally with“depending at least on” and what follows “depending on” or “depending atleast on” indicates an example of one of plurality of usefulalternatives that may be used in an embodiment in this disclosure. Thephrases “employing” and “using” and “employing at least” and “using atleast” may be used equally in this in this disclosure and what follows“employing” or “using” or “employing at least” or “using at least”indicates an example of one of plurality of useful alternatives that maybe used in an embodiment in this disclosure.

The example embodiments disclosed in this disclosure may be implementedusing a modular architecture comprising a plurality of modules. A modulemay be defined in terms of one or more functions and may be connected toone or more other elements and/or modules. A module may be implementedin hardware, software, firmware, one or more biological elements (e.g.,an organic computing device and/or a neurocomputer) and/or a combinationthereof and/or alike. Example implementations of a module may be assoftware code configured to be executed by hardware and/or a modelingand simulation program that may be coupled with hardware. In an example,a module may be implemented using general-purpose or special-purposeprocessors, digital signal processors (DSPs), microprocessors,microcontrollers, application-specific integrated circuits (ASICs),programmable logic devices (PLDs) and/or alike. The hardware may beprogrammed using machine language, assembly language, high-levellanguage (e.g., Python, FORTRAN, C, C++ or the like) and/or alike. In anexample, the function of a module may be achieved by using a combinationof the mentioned implementation methods.

1. A method comprising: receiving, by a wireless device, a radioresource control (RRC) release message comprising: one or more firstconfiguration parameters indicating transitioning from an RRC connectedstate to an RRC inactive state; one or more second configurationparameters to configure a configured grant configuration associated withuplink transmission in the RRC inactive state; and one or more thirdconfiguration parameters indicating a value of a time alignment timerassociated with uplink transmission in the RRC inactive state; startingthe time alignment timer in response to receiving the RRC releasemessage and based on the one or more third configuration parameters; andtransmitting a transport block while in the RRC inactive state: based onradio resources of a first configured grant associated with theconfigured grant configuration; and based on the time alignment timerrunning.
 2. The method of claim 1, wherein the starting the timealignment timer is with the value.
 3. The method of claim 1, wherein thetransmitting the transport block is further based on a timing advancevalue.
 4. The method of claim 1, further comprising activating aplurality of configured grants, comprising the first configured grant,associated with the configured grant configuration in response toreceiving the RRC release message and based on the one or more secondconfiguration parameters.
 5. The method of claim 1, wherein the startingthe time alignment timer is based on a reference timing.
 6. The methodof claim 5, wherein the starting the time alignment timer is based on anoffset to the reference timing.
 7. The method of claim 6, wherein thereference timing is based on a system frame number.
 8. The method ofclaim 1, further comprising: receiving a timing advance commandindicating a first timing advance; and starting the time alignment timerbased on the receiving the timing advance command.
 9. The method ofclaim 8, further comprising transmitting a second transport block basedon radio resources of a second configured grant and based on the firsttiming advance.
 10. The method of claim 1, further comprisingmultiplexing one or more logical channels in the transport block whereinthe one or more logical channels are configured for transmission ofsmall data in the RRC inactive state.
 11. A wireless device comprising:one or more processors; and memory storing instructions that, whenexecuted by the one or more processors, cause the wireless device to:receive a radio resource control (RRC) release message comprising: oneor more first configuration parameters indicating transitioning from anRRC connected state to an RRC inactive state; one or more secondconfiguration parameters to configure a configured grant configurationassociated with uplink transmission in the RRC inactive state; and oneor more third configuration parameters indicating a value of a timealignment timer associated with uplink transmission in the RRC inactivestate; start the time alignment timer in response to receiving the RRCrelease message and based on the one or more third configurationparameters; and transmit a transport block while in the RRC inactivestate: based on radio resources of a first configured grant associatedwith the configured grant configuration; and based on the time alignmenttimer running.
 12. The wireless device of claim 11, wherein starting thetime alignment timer is with the time alignment timer value.
 13. Thewireless device of claim 11, wherein transmitting the transport block isfurther based on a timing advance value.
 14. The wireless device ofclaim 11, wherein the instructions, when executed by the one or moreprocessors, further cause the wireless device to activate a plurality ofconfigured grants, comprising the first configured grant, associatedwith the configured grant configuration in response to receiving the RRCrelease message and based on the one or more second configurationparameters.
 15. The wireless device of claim 11, wherein starting thetime alignment timer is based on a reference timing.
 16. The wirelessdevice of claim 15, wherein the starting the time alignment timer isbased on an offset to the reference timing.
 17. The wireless device ofclaim 16, wherein the reference timing is based on a system framenumber.
 18. The wireless device of claim 11, wherein the instructions,when executed by the one or more processors, further cause the wirelessdevice to: receive a timing advance command indicating a first timingadvance; and start the time alignment timer based on receiving thetiming advance command.
 19. The wireless device of claim 18, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to transmit a second transport block based on radioresources of a second configured grant and based on the first timingadvance.
 20. The wireless device of claim 11, wherein the instructions,when executed by the one or more processors, further cause the wirelessdevice to multiplex one or more logical channels in the transport blockwherein the one or more logical channels are configured for transmissionin the RRC inactive state.